From: Sam Ravnborg <sam@ravnborg•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
Andrew Morton <akpm@linux-foundation•org>,
Linus <torvalds@linux-foundation•org>
Subject: Re: linux-next: kbuild-current build failure
Date: Tue, 10 Jun 2008 21:03:51 +0200 [thread overview]
Message-ID: <20080610190351.GB15983@uranus.ravnborg.org> (raw)
In-Reply-To: <20080610110842.30c90c61.sfr@canb.auug.org.au>
On Tue, Jun 10, 2008 at 11:08:42AM +1000, Stephen Rothwell wrote:
> Hi Sam,
>
> Today's linux-next build (powerpc ppc64_deconfig) failed like this:
>
> LD vmlinux.o
> /scratch/sfr/next/scripts/Makefile.modpost:44: scripts/Kbuild.include: No such file or directory
> /scratch/sfr/next/scripts/Makefile.modpost:58: scripts/Makefile.lib: No such file or directory
> make[2]: *** No rule to make target `scripts/Makefile.lib'. Stop.
> make[1]: *** [vmlinux] Error 2
> make: *** [sub-make] Error 2
>
> This is Linus' tree with just the net-current, arm-current and
> kbuild-current trees merged i.e. just bug fixes queued for Linus' current
> tree. The build was done with "O=../powerpc_ppc64_defconfig -j24 -s"
> i.e. separate object tree and parallel.
>
> Reverting commit 68e9b79c8dad5245f28ab4f3527481b730dbdb61 ("kbuild:
> simplify vmlinux link stage") makes the build work again.
Updated kbuild-next.git pushed out with this bug fixed.
Thanks for reporting/testing it.
Sam
next prev parent reply other threads:[~2008-06-10 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 1:08 linux-next: kbuild-current build failure Stephen Rothwell
2008-06-10 4:33 ` Sam Ravnborg
2008-06-10 4:42 ` Stephen Rothwell
2008-06-10 19:03 ` Sam Ravnborg [this message]
2008-06-10 23:48 ` 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=20080610190351.GB15983@uranus.ravnborg.org \
--to=sam@ravnborg$(echo .)org \
--cc=akpm@linux-foundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=torvalds@linux-foundation$(echo .)org \
/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