I choose embedded target. But config file did not include busybox. I changed the config file like this: X -1-------- 163.500 base busybox 1.6.1 / base/system CROSS INIT 0 but it is failed to build. end up with error: == 10:36:18 =[1]=> Building base/busybox [1.6.1 7.0-rc2]. -> Parallel build using 2 jobs enabled. -> Preparing configuration to build this package with dietlibc (statically). -> Using default dietlibc options! -> Reading package config: package/base/busybox/busybox.conf -> Preparing build in src.busybox.niv.20080115.103618.3674.nameserver -> Building. Writing output to $root/var/adm/logs/1-busybox.out !> libbb/loop.c:50: warning: unused variable 'loopinfo' !> libbb/loop.c: In function 'set_loop': !> libbb/loop.c:85: error: storage size of 'loopinfo' isn't known !> libbb/loop.c:118: error: 'LOOP_GET_STATUS64' undeclared (first use in this .. !> libbb/loop.c:127: error: 'LOOP_SET_STATUS64' undeclared (first use in this .. !> libbb/loop.c:85: warning: unused variable 'loopinfo' !> Due to previous errors, no 1-busybox.log file! !> (Try enabling xtrace in the config to track an error inside the build syst .. -> $root/var/adm/logs/1-busybox.out -> 1-busybox.err == 01/15/08 10:36:55 =[1]=> Aborted building package busybox. -> Unmounting loop mounts ...
This problem is not only with embedded target, it is also with generic system. -- View this message in context: http://www.nabble.com/Busybox-failed-to-build-tp14832238p14832238.html Sent from the T2 mailing list archive at Nabble.com. ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe t2
