From: Emmanuel Fleury <fleury@cs.aau.dk>
To: Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: A Framework to automatically configure a Kernel
Date: Mon, 05 Sep 2005 11:23:51 +0200 [thread overview]
Message-ID: <431C0EA7.8030309@cs.aau.dk> (raw)
In-Reply-To: <20050905084236.46978.qmail@web51011.mail.yahoo.com>
Nice idea !
I really would like to have such feature.
I tried a bit your stuff, unfortunately, I got this:
[fleury@rade7 linux-2.6.13-autoconf]$ make auconfig
HOSTCC scripts/kconfig/auto_conf.o
scripts/kconfig/auto_conf.c: In function 'auto_conf':
scripts/kconfig/auto_conf.c:288: warning: pointer targets in passing
argument 2 of '__builtin_strncpy' differ in signedness
scripts/kconfig/auto_conf.c: In function 'must_have':
scripts/kconfig/auto_conf.c:301: error: syntax error at end of input
make[1]: *** [scripts/kconfig/auto_conf.o] Error 1
make: *** [auconfig] Error 2
Seems that you don't use gcc-4 !
Two questions:
1) Isn't the XML parser a bit overkilling ????
2) Why is the target called "auconfig" and not "autoconfig" (just like
we have a "menuconfig") ?
Speaking about this autoconfig thingy, haven't been any serious attempt
to grab as much information as possible from lspci, /proc, /sys and so
on to build at least a skeleton for the .config ?
Regards
--
Emmanuel Fleury
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it.
-- Brian W. Kernighan
next prev parent reply other threads:[~2005-09-05 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-05 8:42 A Framework to automatically configure a Kernel Ahmad Reza Cheraghi
2005-09-05 9:23 ` Emmanuel Fleury [this message]
[not found] <431C3665.1090002@cs.aau.dk>
2005-09-05 14:50 ` Ahmad Reza Cheraghi
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=431C0EA7.8030309@cs.aau.dk \
--to=fleury@cs.aau.dk \
--cc=linux-kernel@vger.kernel.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