From: Kevin Hilman <khilman@deeprooted.net>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: kbuild, kconfig: forcing values from existing .config
Date: Tue, 11 Jul 2006 14:07:17 -0500 [thread overview]
Message-ID: <1152644837.12527.42.camel@vence.internal.net> (raw)
I'm looking for the right way to override the settings of an existing
default .config. Starting from an existing .config (e.g. generated by a
'make defconfig') I need an automated way of changing specific config
values in order to build a handful of variants based on the same
original .config.
On earlier kernels, I used to just append to the .config, and run 'make
oldconfig' and the appended values would override the existing ones.
This no longer works as 'make oldconfig' now ignores duplicate values.
The allyesconfig/allmodconfig/allnoconfig/randconfig targets allow you
to specify a file containing forced values, but this starts from a clean
slate. I need this same ability to force specific values, but to use an
existing .config as the starting point instead.
Is there currently a way to do this? If so, I can't seem to figure out
how.
Kevin
reply other threads:[~2006-07-11 19:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1152644837.12527.42.camel@vence.internal.net \
--to=khilman@deeprooted.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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®