oups forgot to put CLFS in cc sorry here just in case it could help others:
Hi Andrew, > You should also have a /lib/ld-musl-armhf.so.1 as a symlink to > /lib/libc.so since the compiler is building assuming that the > linker/loader is named ld-musl-armhf.so.1. Does that symlink exist for you? knight@knight:/mnt/clfs$ sudo find cross-tools/ targetfs/ -iname "ld*" cross-tools/share/info/ld.info cross-tools/arm-linux-musleabihf/lib/ldscripts cross-tools/arm-linux-musleabihf/bin/ld cross-tools/arm-linux-musleabihf/bin/ld.bfd sudo find cross-tools/ targetfs/ -iname "*.so" cross-tools/arm-linux-musleabihf/lib/libgcc_s.so cross-tools/arm-linux-musleabihf/lib/libc.so cross-tools/arm-linux-musleabihf/lib/libssp.so cross-tools/arm-linux-musleabihf/lib/libstdc++.so cross-tools/arm-linux-musleabihf/lib/libitm.so cross-tools/arm-linux-musleabihf/lib/libgomp.so cross-tools/libexec/gcc/arm-linux-musleabihf/4.7.3/liblto_plugin.so targetfs/lib/libgcc_s.so targetfs/lib/libc.so targetfs/lib/libssp.so targetfs/lib/libstdc++.so targetfs/lib/libitm.so targetfs/lib/libgomp.so knight@knight:/mnt/clfs/targetfs/lib$ ls -al total 8088 drwxr-xr-x 4 root root 4096 Feb 4 14:57 . drwxr-xr-x 18 root root 4096 Feb 4 14:50 .. drwxr-xr-x 37 root root 4096 Feb 4 14:57 firmware -rwxr-xr-x 1 root root 704053 Feb 4 14:57 libc.so -rw-r--r-- 1 root root 135 Feb 4 14:57 libgcc_s.so -rw-r--r-- 1 root root 1392629 Feb 4 14:57 libgcc_s.so.1 lrwxrwxrwx 1 root root 16 Feb 4 14:57 libgomp.so -> libgomp.so.1.0.0 lrwxrwxrwx 1 root root 16 Feb 4 14:57 libgomp.so.1 -> libgomp.so.1.0.0 -rwxr-xr-x 1 root root 277228 Feb 4 14:57 libgomp.so.1.0.0 lrwxrwxrwx 1 root root 15 Feb 4 14:57 libitm.so -> libitm.so.1.0.0 lrwxrwxrwx 1 root root 15 Feb 4 14:57 libitm.so.1 -> libitm.so.1.0.0 -rwxr-xr-x 1 root root 978507 Feb 4 14:57 libitm.so.1.0.0 lrwxrwxrwx 1 root root 15 Feb 4 14:57 libssp.so -> libssp.so.0.0.0 lrwxrwxrwx 1 root root 15 Feb 4 14:57 libssp.so.0 -> libssp.so.0.0.0 -rwxr-xr-x 1 root root 26079 Feb 4 14:57 libssp.so.0.0.0 lrwxrwxrwx 1 root root 19 Feb 4 14:57 libstdc++.so -> libstdc++.so.6.0.17 lrwxrwxrwx 1 root root 19 Feb 4 14:57 libstdc++.so.6 -> libstdc++.so.6.0.17 -rwxr-xr-x 1 root root 4873993 Feb 4 14:57 libstdc++.so.6.0.17 -rw-r--r-- 1 root root 2348 Feb 4 14:57 libstdc++.so.6.0.17-gdb.py drwxr-xr-x 3 root root 4096 Feb 4 14:57 modules no symlink for /lib/ld-musl-armhf.so.1 in the target. When this symlink is suppose to be created? > > If so, try building a static hello world app and set that to be init. > If that works, that's a good indication that the toolchain is working. > Then try building a dynamically linked hello world, likely if that fails > it'll tell you why (usually related to ld). Found that hello wolrd proposition on busybox mailing list, thx will try... > > If you can run static and dynamic hello world apps as init but busybox > can't, there's something wrong with your busybox build. thx, -KA On Thu, Feb 6, 2014 at 2:17 PM, Andrew Bradford <and...@bradfordembedded.com> wrote: > On 02/06/2014 02:08 PM, Kevyn-Alexandre Paré wrote: > >> no symlink for /lib/ld-musl-armhf.so.1 in the target. When this >> symlink is suppose to be created? > > In section 4.8 (musl-libc), the 'make install' should create it for you > properly as long as you're using DESTDIR as specified in the book. > > So long as you're using a book newer than 20131023, this should work. > Books prior to 20131023 which were musl based required a manual creation > of this symlink due to incorrect 'make install' instructions for the way > musl's install works. > > -Andrew > _______________________________________________ Clfs-support mailing list Clfs-support@lists.cross-lfs.org http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
