[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091009092352.GA7381@elte.hu>
Date: Fri, 9 Oct 2009 11:23:52 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Peter Zijlstra <peterz@...radead.org>
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
* Peter Zijlstra <peterz@...radead.org> 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.
>
> Please revert this.
I'm hitting problems with this several times a day.
I'm used to switching from 32-bit to 64-bit x86 kernels and now i have
to via the extra 'make mrproper' and that's quite annoying as i already
tell kbuild that i want a 64-bit config via:
make ARCH=x86_64 defconfig
Why the extra forced step?
Also, there's things that need even more steps: i often take a config
that triggers a breakage on 32-bit and change it to 64-bit via 'make
oldconfig' - to see whether the bug is bitness invariant. I have to do
something like:
mv .config .config.tmp
make mrproper
mv .config.tmp .config
make ARCH=x86_64 oldconfig
This doesnt look right at all.
Ingo
--
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