Using buildroot to build a system: Hangs after 'Freeing Unused Kernel Memory'

Evert evert at poboxes.info
Tue Jul 4 12:55:58 UTC 2006


Could this be a reason my busybox does not function:

*************************
touch /home/evert/buildroot/build_i586/busybox/.configured
make -j1 CC=/home/evert/buildroot/build_i586/staging_dir/bin/i586-linux-uclibc-gcc CROSS="/home/evert/buildroot/build_i586/staging_dir/bin/i586-linux-uclibc-"
PREFIX="/home/evert/buildroot/build_i586/root" \
        EXTRA_CFLAGS="-Os -pipe " -C /home/evert/buildroot/build_i586/busybox
/bin/sh: line 1: 21721 Segmentation fault      /home/evert/buildroot/build_i586/staging_dir/bin/i586-linux-uclibc-ld -o /dev/null -b binary /dev/null >/dev/null 2>&1
/bin/sh: line 1: 21759 Segmentation fault      /home/evert/buildroot/build_i586/staging_dir/bin/i586-linux-uclibc-ld -o /dev/null -b binary /dev/null >/dev/null 2>&1
/bin/sh: line 1: 21787 Segmentation fault      /home/evert/buildroot/build_i586/staging_dir/bin/i586-linux-uclibc-ld -o /dev/null -b binary /dev/null >/dev/null 2>&1
make[1]: Entering directory `/home/evert/buildroot/build_i586/busybox'
/bin/sh: line 1: 21899 Segmentation fault      /home/evert/buildroot/build_i586/staging_dir/bin/i586-linux-uclibc-ld -o /dev/null -b binary /dev/null >/dev/null 2>&1
/bin/sh: line 1: 21937 Segmentation fault      /home/evert/buildroot/build_i586/staging_dir/bin/i586-linux-uclibc-ld -o /dev/null -b binary /dev/null >/dev/null 2>&1
/bin/sh: line 1: 21969 Segmentation fault      /home/evert/buildroot/build_i586/staging_dir/bin/i586-linux-uclibc-ld -o /dev/null -b binary /dev/null >/dev/null 2>&1

  HOSTLINK scripts/bb_mkdep
*************************

Regards,
  Evert




Evert wrote:
> 
> Mike Frysinger wrote:
>> On Monday 03 July 2006 07:45, Evert wrote:
>>> Why does the system I buit with buildroot hang after 'Freeing Unused Kernel
>>> Memory'?
>> this could be one of many many things ... basically all you know for sure is 
>> userspace isnt working properly, that's it
>>
>> you can start debugging by dropping a static shell that is known to work and 
>> set init= to it at boot
>> -mike
> 
> That worked  :-)
> I copied sash from my host system, and that came up. The 'hello world' trick mentioned at http://www.busybox.net/FAQ.html#init works as well. So I guess my toolchain at least delivers functional
> static code...  ;-)
> 
> 
> Regards,




More information about the uClibc mailing list