From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Sam Ravnborg <sam@ravnborg•org>
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 14:42:39 +1000 [thread overview]
Message-ID: <20080610144239.dab6187e.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080610043348.GB31765@uranus.ravnborg.org>
[-- Attachment #1: Type: text/plain, Size: 849 bytes --]
Hi Sam,
On Tue, 10 Jun 2008 06:33:48 +0200 Sam Ravnborg <sam@ravnborg•org> wrote:
>
> > 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.
>
> This commit is in kbuild-next.git (for the merge window)
> My kbuild-fixes.git is empty at the moment.
Oops, sorry my mistake - I have the same tree listed for kbuild-current
and kbuild (next). :-( I will fix it up for tomorrow.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-06-10 4:42 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 [this message]
2008-06-10 19:03 ` Sam Ravnborg
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=20080610144239.dab6187e.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sam@ravnborg$(echo .)org \
--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