I have tried to compile a few useless configurations (on i686, gcc-2.96) of
the latest kernel and so far found three cases where a valid configuration
fails to compile:
CONFIG_PPP_DEFLATE && (CONFIG_CRAMFS || CONFIG_ZISOFS):
Symbol clashes from two zlib copies (again...). I suppose the symbols in
drivers/net/zlib.c could all be made static unless a merge of both zlib
copies is already planned.
!CONFIG_INET:
Some files in net/core/ are compiled unconditionally, but depend on TCP/IP
(CONFIG_INET). The problem is that TCP_ENC_send in include/net/tcp_ecn.h
accesses the disabled 'af_inet' part of struct sock. A simple #ifdef at the
right place should solve this.
CONFIG_MULTIQUAD && CONFIG_DEBUG_IOVIRT:
arch/i386/boot/compressed/misc.o can't resolve __io_virt_debug (from outb_p)
when linking bzImage. This configuration is really useless and fixing this
would be rather ugly, so I suggest explicitly forbidding it to help the next
fool to try 'yes | make config'.
Arnd <><
[email protected] said:
> CONFIG_PPP_DEFLATE && (CONFIG_CRAMFS || CONFIG_ZISOFS): Symbol
> clashes from two zlib copies (again...). I suppose the symbols in
> drivers/net/zlib.c could all be made static unless a merge of both
> zlib copies is already planned.
JFFS2 will conflict too. JFFS2 and PPP can't use the separate zlib at the
moment, because they require compression support and it only does
decompression. PPP may even have trouble when that's fixed, although I think
we eventually concluded it would be OK.
JFFS2 and PPP can share though.
--
dwmw2