Hello, I've encountered a problem using libtool 1.5.22 to cross-compile on an x86 glibc Linux system, targeting an x86 uClibc Linux system. The build system's /usr/lib is incorrectly getting added to the search path during the relink stage. This problem was described back in January on this list: http://lists.gnu.org/archive/html/bug-libtool/2006-01/msg00002.html
The problem is triggered in the code just past the "We cannot seem to hardcode it, guess we'll fake it." comment. -L/usr/lib is added to the search path if the libdir of one of its dependent libraries is /usr/lib. It seems wrong to search the libdir in a cross-compile environment where libraries are built in one directory, installed into another (inst_prefix_dir/libdir), and are finally copied to libdir by some mechanism external to libtool. I'm currently working around this problem by manually setting hardcode_automatic=yes in my libtool script, which avoids this code. Is there a better workaround, or has the problem been solved in some other way? Thanks, --Ed _______________________________________________ Bug-libtool mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-libtool
