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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |