When booting the target system created by buildroot, I get a lot of "can't load library 'libgcc_s.so.1'" messages. The library exists in the folder /usr/lib64, but it seems that folder is not in the default ld search path. System works fine after copying the library to /lib
Can you send a simple .config reproducing the issue ?
Created attachment 283 [details] .config .config file. Defaults with architecture changed to x86_64, and dropbear selected. In the newest buildroot-20090429 snapshot, is not even installed in the root either, but only appears in the staging dir. == [max@myhost buildroot]$ find project_build_x86_64/uclibc/root |grep libgcc_s [max@myhost buildroot]$ find build_x86_64/staging_dir |grep libgcc_s build_x86_64/staging_dir/usr/x86_64-linux-uclibc/lib64/libgcc_s.so build_x86_64/staging_dir/usr/x86_64-linux-uclibc/lib64/libgcc_s.so.1 == Dropbear (and most other packages, other than busybox), fails to start. Unless you copy the file manually or disable "shared libgcc" in the config.
Quite probably fixed by commit 90c5d156f5414225be756a3e3bff7bb4b532bdf4 Author: Peter Korsgaard <jacmet@sunsite.dk> Date: Thu Jul 2 09:38:56 2009 +0200 toolchain/gcc: ensure libraries are copied to target_dir for x86-64 x86-64 stores libgcc_s / libstdc++ / libgcj under lib64 instead of lib, so make sure that directory is searched as well for libraries to copy to target. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>