public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@gentoo.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux kernel <linux-kernel@vger.kernel.org>,
	kerframil@gmail.com, mpagano@gentoo.org,
	linux-kbuild@vger.kernel.org
Subject: x86: defconfig not being applied automatically in 2.6.24+
Date: Thu, 03 Apr 2008 21:49:02 +0100	[thread overview]
Message-ID: <47F542BE.3000106@gentoo.org> (raw)

In 2.6.23, if you unpacked a kernel source tarball and then ran "make 
menuconfig" you'd be presented with this message:
	# using defaults found in arch/i386/defconfig

and the default options would be set.

The same thing in 2.6.24 does not give you any "using defaults" message, 
and the default config options within menuconfig are rather blank (e.g. 
no PCI support). You can work around this by explicitly running "make 
defconfig" before menuconfig, but it would be nice to have the behaviour 
the way it was for 2.6.23 (and the way it still is for other archs).


I've looked into the problem. It works on 2.6.23 because of init/Kconfig 
which is still unchanged:

config DEFCONFIG_LIST
	[...]
	default "arch/$ARCH/defconfig"

arch/i386/defconfig and arch/x86_64/defconfig existed in 2.6.23, but not 
in 2.6.24 due to the arch merge.

I've identified why it worked in 2.6.23 but I'm not really sure of the 
right way to fix it for the newer kernels. I tried adding another 
default in DEFCONFIG_LIST:
	default "arch/$SRCARCH/configs/$KBUILD_DEFCONFIG"
but it seems that $SRCARCH and $KBUILD_DEFCONFIG are not being exported 
to kconfig and I couldn't immediately see how to change that.

Any thoughts?

Thanks,
Daniel

                 reply	other threads:[~2008-04-03 20:49 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=47F542BE.3000106@gentoo.org \
    --to=dsd@gentoo.org \
    --cc=kerframil@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpagano@gentoo.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