[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1255088484.8802.55.camel@laptop>
Date: Fri, 09 Oct 2009 13:41:24 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Ingo Molnar <mingo@...e.hu>
Cc: Sam Ravnborg <sam@...nborg.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org
Subject: Re: [regressions] Re: kbuild: save ARCH & CROSS_COMPILE when
building a kernel
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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists