From: Peter Zijlstra <peterz@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [regressions] Re: kbuild: save ARCH & CROSS_COMPILE when building a kernel
Date: Fri, 09 Oct 2009 13:41:24 +0200 [thread overview]
Message-ID: <1255088484.8802.55.camel@laptop> (raw)
In-Reply-To: <1255078731.17055.39.camel@laptop>
On Fri, 2009-10-09 at 10:58 +0200, Peter Zijlstra wrote:
> On Sat, 2009-10-03 at 12:34 +0200, Ingo Molnar wrote:
> >
> > that arch-cache thing introduced in:
> >
> > 5755433: kbuild: save ARCH & CROSS_COMPILE when building a kernel
> >
> > isnt working very well in my experience.
>
> Its breaking things for me too. When I build a .config using distcc and
> cross compilers on my build farm, and then try a make install on another
> machine which doesn't have either it utterly shits itself.
It also wrecks the online/offline workflow I have.
When connected with 10gbe I use the build cluster from my laptop, when
wireless or offline I clearly cannot use distcc.
My scripts automagically do this right, except now they barf.
It basically means I have to now script around this crap by trap'ing the
build script and always deleting the $BUILD_DIR/include/generated crap.
Is there really anybody out there who hasn't scripted their distcc/cross
build stuff and types that incredibly long make line every time?
next prev parent reply other threads:[~2009-10-09 11:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 10:34 [regressions] Re: kbuild: save ARCH & CROSS_COMPILE when building a kernel Ingo Molnar
2009-10-04 19:17 ` Sam Ravnborg
2009-10-09 9:26 ` Ingo Molnar
2009-10-11 21:35 ` Sam Ravnborg
2009-10-12 20:44 ` Ingo Molnar
2009-10-12 21:08 ` Sam Ravnborg
2009-10-12 21:12 ` Ingo Molnar
2009-10-09 8:58 ` Peter Zijlstra
2009-10-09 9:23 ` Ingo Molnar
2009-10-09 11:41 ` Peter Zijlstra [this message]
2009-10-11 9:05 ` Pavel Machek
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=1255088484.8802.55.camel@laptop \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.org \
/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