linux-kernel - Re: linux-next: build failure after merge of the kbuild tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 9 Sep 2022 15:48:55 +0900
From:   Masahiro Yamada <masahiroy@...nel.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the kbuild tree

On Fri, Sep 9, 2022 at 3:14 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi,
>
> On Fri, 9 Sep 2022 15:24:53 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > On Fri, 9 Sep 2022 14:10:06 +0900 Masahiro Yamada <masahiroy@...nel.org> wrote:
> > >
> > > Hmm, I am testing allmodconfig in my tree,
> > > but it is not reproducible so far.
> > >
> > > Do you have any more hint?
> > > (which commit exactly?, and what build command did you use? etc.)
> >
> > I was trying your top of tree commit
> >
> >   99ea8da56dca "kbuild: use objtool-args-y to clean up objtool arguments"
> >
> > (merged with Linus' tree and some fix patches).
> >
> > I am doing a cross build with an out of tree object directory:
> >
> > $ make ARCH=x86_64 CROSS_COMPILE=x86_64-linux-gnu- O=../x86_64_allmodconfig -s allmodconfig
> > $ make ARCH=x86_64 CROSS_COMPILE=x86_64-linux-gnu- O=../x86_64_allmodconfig -j100 -O -s
>
> So it seems to be related to doing an incremental build.  I have just
> built my "pending-fixes" branch (which I have pushed out to the
> linux-next tree on git.kernel.org), then merged your tree and then
> built again:

I tried this.

I built fa8e6bb658f682ff63b3af3dd4c5e4d3b43f4ffd (pending-fixes) first,
then merged b326faa3e125.



masahiro@...ar:~/ref/linux-next$ git show --pretty=fuller
commit ca2e36215ba55dab29160cfe0512b5a8a172efe0 (HEAD -> merge-kbuild)
Merge: fa8e6bb658f6 b326faa3e125
Author:     Masahiro Yamada <masahiroy@...nel.org>
AuthorDate: Fri Sep 9 15:41:07 2022 +0900
Commit:     Masahiro Yamada <masahiroy@...nel.org>
CommitDate: Fri Sep 9 15:41:07 2022 +0900

    Merge ../../workspace/linux-kbuild into merge-kbuild



>
> $ make ARCH=x86_64 CROSS_COMPILE=x86_64-linux-gnu- O=../obj -j15 -O
> make[1]: Entering directory '/home/sfr/kernels/obj'
>   GEN     Makefile
> make[1]: Leaving directory '/home/sfr/kernels/obj'
> make[1]: Entering directory '/home/sfr/kernels/obj'
>   UPD     include/generated/compile.h
> make[1]: Leaving directory '/home/sfr/kernels/obj'


Weird 'Entering/Leaving directory' logs.






In my case, it went quite normally.

I see only one 'Entering directory', with no error.



masahiro@...ar:~/ref/linux-next$ make ARCH=x86_64
CROSS_COMPILE=x86_64-linux-gnu- O=../obj  -j24
make[1]: Entering directory '/home/masahiro/ref/obj'
  GEN     Makefile
  DESCEND objtool
  CALL    /home/masahiro/ref/linux-next/scripts/atomic/check-atomics.sh
  CALL    /home/masahiro/ref/linux-next/scripts/checksyscalls.sh
  CHK     include/generated/compile.h










>   DESCEND objtool
> make[2]: *** No rule to make target 'objtool/objtool'.  Stop.
> make[1]: *** [/home/sfr/kernels/test/Makefile:1361: tools/objtool/objtool] Error 2
> make[1]: *** Waiting for unfinished jobs....
> make: *** [Makefile:222: __sub-make] Error 2
>
> (I actually did this on my laptop rather than my build machine, but the
> compiles are still cross compiles - just from arm64 instead of
> powerpc64le).
> --
> Cheers,
> Stephen Rothwell



-- 
Best Regards
Masahiro Yamada