From: Masahiro Yamada <masahiroy@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the kbuild tree
Date: Fri, 9 Sep 2022 15:48:55 +0900 [thread overview]
Message-ID: <CAK7LNATR0-Y_yHTcD62J4N36T-_4G=-N1me8EWYNTNYbwXerDw@mail.gmail.com> (raw)
In-Reply-To: <20220909161354.2c94a495@canb.auug.org.au>
On Fri, Sep 9, 2022 at 3:14 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi,
>
> On Fri, 9 Sep 2022 15:24:53 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > On Fri, 9 Sep 2022 14:10:06 +0900 Masahiro Yamada <masahiroy@kernel.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@oscar:~/ref/linux-next$ git show --pretty=fuller
commit ca2e36215ba55dab29160cfe0512b5a8a172efe0 (HEAD -> merge-kbuild)
Merge: fa8e6bb658f6 b326faa3e125
Author: Masahiro Yamada <masahiroy@kernel.org>
AuthorDate: Fri Sep 9 15:41:07 2022 +0900
Commit: Masahiro Yamada <masahiroy@kernel.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@oscar:~/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
next prev parent reply other threads:[~2022-09-09 6:49 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 23:00 linux-next: build failure after merge of the kbuild tree Stephen Rothwell
2022-09-09 5:10 ` Masahiro Yamada
2022-09-09 5:24 ` Stephen Rothwell
2022-09-09 6:13 ` Stephen Rothwell
2022-09-09 6:48 ` Masahiro Yamada [this message]
2022-09-09 7:49 ` Stephen Rothwell
[not found] ` <CAK7LNARiW66Hk5JJgRYb-edkb6sgTWPbNr1iETkq-RASCo-YkA@mail.gmail.com>
2022-09-11 23:55 ` Stephen Rothwell
2022-09-12 5:06 ` Masahiro Yamada
2022-09-12 7:43 ` Stephen Rothwell
2022-09-09 8:26 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2022-10-14 1:42 Stephen Rothwell
2022-10-14 13:31 ` Masahiro Yamada
2022-10-12 22:17 Stephen Rothwell
2022-10-12 22:34 ` Masahiro Yamada
2022-10-12 23:51 ` Stephen Rothwell
2022-09-08 0:06 Stephen Rothwell
2022-09-08 4:14 ` Masahiro Yamada
2022-09-07 12:34 Stephen Rothwell
2022-09-07 13:49 ` Masahiro Yamada
2022-05-23 10:59 Stephen Rothwell
2022-05-23 15:59 ` Masahiro Yamada
2021-08-26 9:13 Stephen Rothwell
2021-08-27 0:52 ` Masahiro Yamada
2021-08-27 1:50 ` Stephen Rothwell
2021-08-27 2:49 ` Masahiro Yamada
2021-02-21 21:33 Stephen Rothwell
2021-02-21 23:21 ` Masahiro Yamada
2020-07-07 7:07 Stephen Rothwell
2020-07-13 1:56 ` Stephen Rothwell
2020-07-13 7:52 ` Masahiro Yamada
2020-04-06 2:34 Stephen Rothwell
2020-04-07 4:41 ` Masahiro Yamada
2020-03-10 22:53 Stephen Rothwell
2020-03-11 4:22 ` Masahiro Yamada
2019-07-16 4:31 Stephen Rothwell
2019-07-16 4:59 ` Masahiro Yamada
2019-07-16 6:42 ` Stephen Rothwell
2019-07-05 8:31 Stephen Rothwell
2019-07-06 0:05 ` Michael Kelley
2019-07-06 0:58 ` Masahiro Yamada
2019-05-05 23:46 Stephen Rothwell
2019-05-05 23:35 Stephen Rothwell
2019-05-05 22:40 Stephen Rothwell
2018-08-22 22:35 Stephen Rothwell
2018-08-23 9:03 ` Masahiro Yamada
2018-05-30 1:29 Stephen Rothwell
2018-05-30 1:44 ` Masahiro Yamada
2018-05-15 5:50 Stephen Rothwell
2018-05-16 6:01 ` Masahiro Yamada
2018-05-16 7:26 ` Stephen Rothwell
2018-05-17 13:45 ` Masahiro Yamada
2018-03-28 21:58 Stephen Rothwell
2018-03-29 1:59 ` Masahiro Yamada
2016-09-15 6:08 Stephen Rothwell
2016-09-22 12:52 ` Michal Marek
2016-07-28 2:08 Stephen Rothwell
2016-07-28 2:40 ` Michael Ellerman
2016-03-15 23:58 Stephen Rothwell
2016-03-16 7:53 ` Daniel Wagner
2016-03-16 7:56 ` Michal Marek
2016-03-16 11:29 ` Stephen Rothwell
2016-03-16 11:31 ` Michal Marek
2013-02-24 23:56 Stephen Rothwell
2013-02-25 10:28 ` Michal Marek
2013-02-25 10:58 ` Stephen Rothwell
2013-02-25 11:02 ` Stephen Rothwell
2013-02-25 11:36 ` Michal Marek
2011-04-19 22:25 Stephen Rothwell
2011-04-19 22:30 ` Stephen Rothwell
2011-04-20 13:50 ` Michal Marek
2010-03-11 5:15 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='CAK7LNATR0-Y_yHTcD62J4N36T-_4G=-N1me8EWYNTNYbwXerDw@mail.gmail.com' \
--to=masahiroy@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).