public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <peterz@infradead.org>
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, 9 Oct 2009 11:23:52 +0200	[thread overview]
Message-ID: <20091009092352.GA7381@elte.hu> (raw)
In-Reply-To: <1255078731.17055.39.camel@laptop>


* Peter Zijlstra <peterz@infradead.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

  reply	other threads:[~2009-10-09  9:24 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 [this message]
2009-10-09 11:41   ` Peter Zijlstra
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=20091009092352.GA7381@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --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