public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Sam Ravnborg <sam@ravnborg.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [regressions] Re: kbuild: save ARCH & CROSS_COMPILE when building a kernel
Date: Sat, 3 Oct 2009 12:34:41 +0200	[thread overview]
Message-ID: <20091003103441.GA10874@elte.hu> (raw)


Sam,

that arch-cache thing introduced in:

 5755433: kbuild: save ARCH & CROSS_COMPILE when building a kernel

isnt working very well in my experience.

1) it's a nuisance in cross-builds (it broke several cross-build scripts 
   of mine)

2) it makes it hard to switch from 32-bit x86 builds to 64-bit ones: 
   previously i only needed 'make ARCH=i386 defconfig' and off we went - 
   now i have to add a 'make mrproper' step.

3) it can also get stuck:

  phoenix:~/linux/linux> make mrproper
  Makefile:571: /home/mingo/tip/arch/no/Makefile: No such file or directory
  make: *** No rule to make target `/home/mingo/tip/arch/no/Makefile'.  Stop.

  phoenix:~/linux/linux> cat include/generated/*
  no

  phoenix:~/linux/linux> 

 There's no way out of this state, only if i manually remove 
 include/generated. (i suspect this is fixable)

Dunno - why isnt the .config enough in terms of determining which 
architecture we are on? If we want more info we should put it into the 
.config - not some other hidden state. I do think a single file should 
carry all 'configuration state' - that makes it easier to reproduce 
things, etc. etc. Everything else is really just hindering us.

	Ingo

             reply	other threads:[~2009-10-03 10:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-03 10:34 Ingo Molnar [this message]
2009-10-04 19:17 ` [regressions] Re: kbuild: save ARCH & CROSS_COMPILE when building a kernel 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
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=20091003103441.GA10874@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.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