From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: sam@ravnborg.org
Cc: linux-kernel@vger.kernel.org
Subject: Kconfig no longer outputs a .config with freshly updated defconfigs
Date: Sat, 02 Aug 2008 12:03:33 -0400 [thread overview]
Message-ID: <1217693013.2328.22.camel@localhost.localdomain> (raw)
I was going through the somewhat tedious task of updating the 4xx
defconfigs today, and I noticed some odd behavior from Kconfig.
Basically, I would do:
make ppc44x_defconfig
make oldconfig
<build>
cp .config arch/powerpc/configs/ppc44x_defconfig
make distclean
I did this for a number of configs. Then I went back and tried to build
ppc44x_defconfig again and I got this result:
[jwboyer@localhost linux-2.6]$ make ppc44x_defconfig
HOSTCC scripts/basic/fixdep
HOSTCC scripts/basic/docproc
HOSTCC scripts/kconfig/conf.o
HOSTCC scripts/kconfig/kxgettext.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/lex.zconf.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
scripts/kconfig/lex.zconf.c:1628: warning: ‘input’ defined but not used
HOSTLD scripts/kconfig/conf
[jwboyer@localhost linux-2.6]$ make oldconfig
scripts/kconfig/conf -o arch/powerpc/Kconfig
#
# using defaults found in /boot/config-2.6.25.13-104.fc9.ppc64
#
There was no .config file present after the initial 'make
ppc44x_defconfig', so it defaulted to using something in /boot. I'm a
bit baffled here, but that seems to be common to any newly updated
defconfig I've done.
Was there a change to Kconfig recently that won't copy the defconfig
file to .config if there are no symbol changes or something like that?
josh
next reply other threads:[~2008-08-02 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 16:03 Josh Boyer [this message]
2008-08-02 19:26 ` Adrian Bunk
2008-08-02 23:58 ` Josh Boyer
2008-08-03 8:00 ` Sam Ravnborg
2008-08-03 10:07 ` Adrian Bunk
2008-08-04 21:08 ` Sam Ravnborg
2008-08-05 2:50 ` Roman Zippel
2008-08-05 20:43 ` Sam Ravnborg
2008-08-09 5:26 ` 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=1217693013.2328.22.camel@localhost.localdomain \
--to=jwboyer@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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
Powered by JetHome