All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Blaisorblade <blaisorblade@yahoo.it>
Subject: Re: [uml-devel] [patch] Remove unnecessary config symbol from makefile.
Date: Sun, 20 Mar 2005 17:24:33 -0500	[thread overview]
Message-ID: <200503201724.35155.rob@landley.net> (raw)
In-Reply-To: <200503201142.17480.blaisorblade@yahoo.it>

On Sunday 20 March 2005 05:42 am, Blaisorblade wrote:

> > Without the fix I posted, I have to remove existing
> > symbols from the list,
>
> If you enable the other symbol, Kbuild will remove it from .config for you
> (and output a warning message, yes, but that's hardly a problem). When I
> remove config options from Kconfig files I don't need to remove them
> from .config by hand...

How does oldconfig know which one "wins" when they're both set in the .config?  
I'm not running menuconfig, I have a script that is appending more symbols to 
the .config file, which works fine for normal symbols (ones that are 
commented out when they're not set), and I'm starting with a "make 
allnoconfig" that I then append extra symbols to and run make oldconfig to 
resolve dependencies...

Trying to set up something with make config and expect would be more brittle 
and version specific than just snapshotting a .config file in the first 
place, and would defeat the purpose anyway.  The point is, I wanted my build 
script to be self-documenting about what symbols it needed.  The ones it 
appends are the ones it needs, and the ones you'd have to switch on by hand 
if you did a make allnoconfig followed by make menuconfig yourself..

See what I'm getting at?

If you're saying that there's a hard rule that any symbol that's set by make 
allnoconfig will automatically lose to any other symbol that isn't if both 
are set in the config and oldconfig has to resolve an inconsistent state, I 
suppose I can live with that.  I'm a bit uncomfortable relying on that unless 
it's documented somewhere...

Rob


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      reply	other threads:[~2005-03-20 23:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17  7:19 [uml-devel] [patch] Remove unnecessary config symbol from makefile Rob Landley
2005-03-17 19:22 ` Blaisorblade
2005-03-17 23:59   ` Rob Landley
2005-03-20 10:42     ` Blaisorblade
2005-03-20 22:24       ` Rob Landley [this message]

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=200503201724.35155.rob@landley.net \
    --to=rob@landley.net \
    --cc=blaisorblade@yahoo.it \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.