I found that gcc in cvs (HEAD in 2005/02/11) reject the ifupdown/inetd source
in the busybox.
This may be caused by changing gcc's error handling behavior(
The gcc check the function prototype more strictly).
I show the compilation log as follow:
-- ifupdown
/home/ares/cross/expr/i686/bin/i686-unknown-linux-gnu-gcc -I/home2/ares/temp/busybox/busybox-current.fix/include -I/home2/ares/temp/busybox/busybox-current.fix/include -I/home2/ares/temp/busybox/busybox-current.fix/libbb -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Wall -Wstrict-prototypes -Wshadow -Os -march=i386 -mpreferred-stack-boundary=2 -falign-functions=0 -falign-jumps=0 -falign-loops=0 -fomit-frame-pointer -D_GNU_SOURCE -DNDEBUG -O2 -c -o /home2/ares/temp/busybox/busybox-current.fix/networking/ifupdown.o /home2/ares/temp/busybox/busybox-current.fix/networking/ifupdown.c
/home2/ares/temp/busybox/busybox-current.fix/networking/ifupdown.c:153: error: static declaration of 'environ' follows non-static declaration
/home2/ares/cross/expr/i686/bin/../target_root/usr/include/unistd.h:476: error: previous declaration of 'environ' was here
make: *** [/home2/ares/temp/busybox/busybox-current.fix/networking/ifupdown.o]
-- ifupdown
-- inetd
/home2/ares/temp/busybox/busybox-current.fix/networking/inetd.c: In function 'config':
/home2/ares/temp/busybox/busybox-current.fix/networking/inetd.c:579: error: invalid lvalue in assignment
/home2/ares/temp/busybox/busybox-current.fix/networking/inetd.c:579: error: invalid lvalue in assignment
-- inetd
busybox-networking-with-gcc-4.0-fix.patch [^] (926 bytes) 02-11-05 13:17 
