public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Masahiro Yamada <yamada.masahiro@socionext•com>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: occassional build errors
Date: Thu, 4 Oct 2018 10:39:37 +1000	[thread overview]
Message-ID: <20181004103937.5601c02a@canb.auug.org.au> (raw)
In-Reply-To: <20181003165534.4bc87bbe@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 2161 bytes --]

Hi Masahiro,

On Wed, 3 Oct 2018 16:55:34 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> > >  The latest example is this:
> > >
> > > include/linux/kconfig.h: file not recognized: file format not recognized
> > > make[2]: *** [scripts/Makefile.build:492: crypto/crypto_user.o] Error 1
> > > make[1]: *** [Makefile:1057: crypto] Error 2
> > > make: *** [Makefile:152: sub-make] Error 2
> > > Command exited with non-zero status 2
> > >
> > > It is always complaining about a .h file ...
> > >
> > > Makefile:152 is the MAKE lien below:
> > >
> > > # Invoke a second make in the output directory, passing relevant variables
> > > sub-make:
> > >         $(Q)$(MAKE) -C $(KBUILD_OUTPUT) KBUILD_SRC=$(CURDIR) \
> > >         -f $(CURDIR)/Makefile $(filter-out _all sub-make,$(MAKECMDGOALS))
> > >
> > > Makefile:1057 is the MAKE line below:
> > >
> > > PHONY += $(vmlinux-dirs)
> > > $(vmlinux-dirs): prepare scripts
> > >         $(Q)$(MAKE) $(build)=$@ need-builtin=1
> > >
> > > scripts/Makefile.build:492 is the if_changed line below:
> > >
> > > $(multi-used-m): FORCE
> > >         $(call if_changed,link_multi-m)
> > >         @{ echo $(@:.o=.ko); echo $(filter-out FORCE,$^); \
> > >            $(cmd_undef_syms); } > $(MODVERDIR)/$(@F:.o=.mod)
> > > $(call multi_depend, $(multi-used-m), .o, -objs -y -m)
> > >
> > > Not sure what else I can tell you.  
> > 
> > Does this happen only when building a module?  
> 
> I don't know, sorry, I build with -s and -j80, so it is hard to tell
> what it is currently up to.

Today, I got this from the x86_64 allmodconfig build after merging the hid tree:

x86_64-linux-gnu-ld: include/config/acpi.h: file not recognized: file truncated
make[4]: *** [/home/sfr/next/next/scripts/Makefile.build:492: drivers/hid/i2c-hid/i2c-hid.o] Error 1
make[3]: *** [/home/sfr/next/next/scripts/Makefile.build:520: drivers/hid/i2c-hid] Error 2
make[2]: *** [/home/sfr/next/next/scripts/Makefile.build:520: drivers/hid] Error 2
make[1]: *** [/home/sfr/next/next/Makefile:1057: drivers] Error 2
make: *** [Makefile:152: sub-make] Error 2

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-10-04  0:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-03  3:50 linux-next: occassional build errors Stephen Rothwell
2018-10-03  4:31 ` Masahiro Yamada
2018-10-03  6:55   ` Stephen Rothwell
2018-10-04  0:39     ` Stephen Rothwell [this message]
2018-10-04  1:56       ` Stephen Rothwell
2018-10-04  3:09         ` Masahiro Yamada
2018-10-04  3:41           ` Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181004103937.5601c02a@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=yamada.masahiro@socionext$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox