mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: blaisorblade_spam@yahoo.it, akpm@osdl.org,
	linux-kernel@vger.kernel.org, julian@sektor37.de,
	mcr@sandelman.ottawa.on.ca, sam@ravnborg.org
Subject: Re: [patch 2/2] kbuild: fix crossbuild base config
Date: Wed, 3 Nov 2004 19:19:37 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.61.0411031909460.877@scrub.home> (raw)
In-Reply-To: <20041103174856.GG381@smtp.west.cox.net>

Hi,

On Wed, 3 Nov 2004, Tom Rini wrote:

> > > This has actually created not-working UML binaries (since UML is always
> > > "cross-compiled" for this purpose), as reported by Julian Scheid.
> > 
> > This rather suggests, there is a problem with UML. Either fix your Kconfig 
> > to prevent nonvalid configurations or detect and report the problem at 
> > runtime.
> 
> No, this is a damn annoying kbuild problem when cross compiling.

The ability to create a nonworkable UML binary is _not_ a kbuild problem, 
especially in the UML case I would expect it should be possible to avoid 
this.

> > > We all agreed on this kind of general, not UML-only fix, and I (Paolo)
> > > implemented it.
> > 
> > I don't like the two separate lists, it would be easier to just skip all 
> > absolute path names.
> > I would also like to avoid this patch at all. If this really should be a 
> > problem, I'd consider to don't run kconfig at all in this case if there 
> > is no configuration and instead suggest running defconfig (or one of 
> > machine specific config targets) first.
> 
> I have a feeling that changing the behavior of 'make {,x,g,q}config' to
> fail if there's no .config will upset a lot of users, possibly even more
> than would be upset by never looking in /boot or /lib ever.

I'm only talking about cross compiling here. From people who do this, I 
sort of expect, that they know what they do. You can misconfigure a kernel 
in native compiles as well, this patch solves the wrong problem. 
E.g. if someone wrote a patch which stores the arch in .config and warns/ 
refuses to load it for a different configuration, I would accept it 
happily.

bye, Roman

  reply	other threads:[~2004-11-03 18:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-02 23:20 blaisorblade_spam
2004-11-03 16:56 ` Roman Zippel
2004-11-03 17:48   ` Tom Rini
2004-11-03 18:19     ` Roman Zippel [this message]
2004-11-03 18:34       ` Tom Rini
2004-11-03 20:32         ` Blaisorblade
2004-11-04  0:06           ` Roman Zippel
2004-11-04  0:04         ` Roman Zippel

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=Pine.LNX.4.61.0411031909460.877@scrub.home \
    --to=zippel@linux-m68k.org \
    --cc=akpm@osdl.org \
    --cc=blaisorblade_spam@yahoo.it \
    --cc=julian@sektor37.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcr@sandelman.ottawa.on.ca \
    --cc=sam@ravnborg.org \
    --cc=trini@kernel.crashing.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

all inboxes | Powered by JetHome®