The libgcc_s.so symlink gets created as a path to /targets/<target-name>/lib/libgcc_s.so.1 instead of as a link to ../../lib/libgcc_s.so.1. This makes a rootstrap created from <target-name> basically broken. It'll work if the user of the rootstrap has a target named, and configured, the same, but that's a pretty big "if".
I took a look at target_setup.sh, and the problem appears to be in the for-loop for tc_libs. If I change the name of the lib and its symlink to be what looks to be expected (ie., change the real file's name to libgcc_s- 1.0.so and the symlink to be libgcc_s.so.1 and add a symlink in the toolchain's libc/usr/lib called libgcc_s.so) then it all gets created correctly during the install -c. So it looks like libgcc_s.so is an exception to whatever "rule" the regular expression is trying to adhere to. But since I'm not sure what that rule really is, I'm hesitant to change anything about it myself. Diane
_______________________________________________ Scratchbox-devel mailing list [email protected] http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-devel
