Hi,
I've been away from the project for a few months. The last days I wanted to build a new image with the following new features:
1. IMQ
2. SIP nat
I can only compile when I replace $(SNAPSHOT) to snapshot in buildroot/Makefile:
SNAPSHOT:=20041031
ARCH:=mipsel
USE_UCLIBC_SNAPSHOT:=snapshot <---
USE_UCLIBC_LDSO_0_9_24:=false
USE_BUSYBOX_SNAPSHOT:=snapshot <---
USE_NETFILTER_SNAPSHOT:=20041009
USE_BRIDGE_VERSION:=1.0.4
BUILD_WITH_LARGEFILE:=true
I have download a new buildroot-tree via cvs yesterday. The changes I have made are these I have mentioned above, nothing else.
uclibc compiles. I had to answer a question regarding security extensions. I have answered it with N, as suggested.
busybox does not compile:
/home/openwrt/buildroot/build_mipsel/staging_dir/bin/mipsel-linux-uclibc-gcc -I/home/openwrt/buildroot/build_mipsel/busybox/include -I/home/openwrt/buildroot/build_mipsel/busybox/include -I/home/openwrt/buildroot/build_mipsel/busybox/libbb -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Wall -Wstrict-prototypes -Wshadow -Os -fomit-frame-pointer -D_GNU_SOURCE -DNDEBUG -Os -Os -mips2 -fomit-frame-pointer -c -o /home/openwrt/buildroot/build_mipsel/busybox/libbb/loop.o /home/openwrt/buildroot/build_mipsel/busybox/libbb/loop.c
In file included from /home/openwrt/buildroot/build_mipsel/busybox/libbb/loop.c:22:
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h:53: error: parse error before "__kernel_fd_set"
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h: In function `__FD_SET':
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h:55: error: `__fd' undeclared (first use in this function)
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h:55: error: (Each undeclared identifier is reported only once
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h:55: error: for each function it appears in.)
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h:55: error: `__NFDBITS' undeclared (first use in this function)
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h:57: error: `__fdsetp' undeclared (first use in this function)
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h: At top level:
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h:61: error: parse error before "__kernel_fd_set"
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h: In function `__FD_CLR':
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h:63: error: `__fd' undeclared (first use in this function)
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h:63: error: `__NFDBITS' undeclared (first use in this function)
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h:65: error: `__fdsetp' undeclared (first use in this function)
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h: At top level:
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h:69: error: parse error before '*' token
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h: In function `__FD_ISSET':
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h:71: error: `__fd' undeclared (first use in this function)
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h:71: error: `__NFDBITS' undeclared (first use in this function)
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h:73: error: `__p' undeclared (first use in this function)
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h: At top level:
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h:81: error: parse error before '*' token
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h: In function `__FD_ZERO':
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h:83: error: `__p' undeclared (first use in this function)
/home/openwrt/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/sys-include/asm/posix_types.h:86: error: `__FDSET_LONGS' undeclared (first use in this function)
make[1]: *** [/home/openwrt/buildroot/build_mipsel/busybox/libbb/loop.o] Error 1
make[1]: Leaving directory `/home/openwrt/buildroot/build_mipsel/busybox'
make: *** [/home/openwrt/buildroot/build_mipsel/busybox/busybox] Error 2
This is why I would like to ask for version numbers of at least the uclibc- and the buysbox-package. I personally think this forum is a good place to start a discussion when I suggest the following:
- OpenWRT-build-versions with a list of working software and their version numbers
- A standard for kernel-patches. Those of you who read the patches distributed in this forum and are not expert-developers can maybe understand my difficulties with lines like these in patch-files:
--- linux/net/sched/sch_htb.c 2003-10-14 01:09:35.000000000 -0700
+++ linux.2.4.26/net/sched/sch_htb.c 2004-05-10 00:05:51.000000000 -0700
- A standard or skeleton-patchfile for patching software
- A publically readable and centrally maintained list of patches that have been included into buildroot and others that are available but have not been included.
- A central repository for all this. If there's the need for space and manpower, I can offer it.
I think we all would benefit from standards and documentation for this valuable project. What you think? Additional suggestions, pure criticism, deep anger or warm "d'accord"? Let us all know...
case
who's rather on wire or waves then on code...