From: Russell King <rmk@arm.linux.org.uk>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Sam Ravnborg <sam@ravnborg.org>, linux-kernel@vger.kernel.org
Subject: Re: kconfig: Locate files relative to $srctree
Date: Sun, 24 Nov 2002 13:37:41 +0000 [thread overview]
Message-ID: <20021124133741.A29087@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0211240250490.2113-100000@serv>; from zippel@linux-m68k.org on Sun, Nov 24, 2002 at 02:56:22AM +0100
On Sun, Nov 24, 2002 at 02:56:22AM +0100, Roman Zippel wrote:
> > const char *conf_confnames[] = {
> > ".config",
> > "/lib/modules/$UNAME_RELEASE/.config",
> > "/etc/kernel-config",
> > "/boot/config-$UNAME_RELEASE",
> > - conf_defname,
> > + "arch/$ARCH/defconfig", /* index DEFNAME */
> > + "$" SRCTREE "/arch/$ARCH/defconfig", /* index DEFALTNAME */
> > NULL,
> > };
>
> This is not good. At some point I maybe want to make these configurable.
> I changed the patch to always use zconf_fopen(), which will try the
> alternative prefix for relative paths.
> I couldn't test this very much as you forgot the kbuild script. :)
> Anyway, below is an alternative version.
One thing that does slightly annoy me with the new config tools is the
handling of the default configuration when you're cross-building. In
this circumstance, looking for the running kernel configuration seems
wrong; it definitely isn't going to be the configuration you want to
start from.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-11-24 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-23 22:07 kconfig: Locate files relative to $srctree Sam Ravnborg
2002-11-24 1:56 ` Roman Zippel
2002-11-24 13:37 ` Russell King [this message]
2002-11-24 14:23 ` Roman Zippel
2002-11-26 19:29 ` Sam Ravnborg
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=20021124133741.A29087@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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 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.