Khem Raj <raj.khem <at> gmail.com> writes: > > could be that its from one of intermediate gcc stages. > libgcc_s.so.1 is provided by both the host package gcc-cross-sdk and the target package libgcc1, both installed to the same place.
[r...@msvm1 powerpc-angstrom-linux]# opkg files gcc-cross-sdk | grep libgcc /usr/local/angstrom/powerpc/powerpc-angstrom-linux/lib/libgcc_s.so /usr/local/angstrom/powerpc/powerpc-angstrom-linux/lib/nof/libgcc_s.so.1 /usr/local/angstrom/powerpc/lib/gcc/powerpc-angstrom-linux/4.3.3/libgcc.a /usr/local/angstrom/powerpc/powerpc-angstrom-linux/lib/libgcc_s.so.1 /usr/local/angstrom/powerpc/powerpc-angstrom-linux/lib/nof/libgcc_s.so /usr/local/angstrom/powerpc/lib/gcc/powerpc-angstrom-linux/4.3.3/libgcc_eh.a [r...@msvm1 powerpc-angstrom-linux]# opkg-target files libgcc1 Package libgcc1 (4.3.3-r7.1.4) is installed on root and has the following files: /usr/local/angstrom/powerpc/powerpc-angstrom-linux/lib/libgcc_s.so.1 Since the files in the image directory of gcc-cross-sdk are correct, I suspect that it is the fault of libgcc1. I am looking into this further today...after I get past the latest meta-toolchain build issue... :) -jeremy _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
