I've been using the supplied ARM EABI compiler (scratchbox-toolchain-arm-gcc3.44csn-glibc2.3). For reference: this is a toolchain built using the "alien-tc" harness; the underlying compiler and binutils are a binary download from CodeSourcery's website.
When compiling most packages, things go normally. Occasionally, though, the linker will fail to find libraries specified with "-lfoo" despite a correctly positioned libfoo.so (and the libfoo.so.X to which it points) in /usr/lib. These linkage problems can be worked around by manually telling the compiler to look in /usr/lib (LDFLAGS="-Wl,-rpath,/usr/lib" when using an autotools build system). This seems somewhat artificial, because /usr/lib is (or ought to be?) the default search path for the linker, and for most linking requests one doesn't have to intervene with the -rpath switch. Is this likely just fallout from the fact that this toolchain is pre-built and possibly not configured to always consult /usr/lib? _______________________________________________ Scratchbox-users mailing list Scratchbox-users@lists.scratchbox.org http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
