|
From: | Aleksandar Milivojevic |
Subject: | Re: libtool not hardlinking library path on sparc*-sun-solaris* |
Date: | Fri, 13 Jan 2006 09:17:03 -0600 |
User-agent: | Internet Messaging Program (IMP) H3 (4.0.4) |
Quoting Ralf Wildenhues <address@hidden>:
Hi Aleksandar, * Aleksandar Milivojevic wrote on Thu, Jan 12, 2006 at 04:49:48PM CET:I've a problem with libtool (1.5.22 and the version included with gcc 4.0.2). Platform is sparc*-sun-solaris*. Using gcc 4.0.2. The linker doesn't seem to influence it (I've had same problem with gcc build that uses Sun ld and the build that uses Gnu ld). When creating shared libraries, the library path is not hardcoded into executable. On Solaris system, this may result in dynamic linker failing to load dynamic libraries during runtime../libtool --mode=link gcc -o libfoo.la -rpath /prefix/lib list-of-files gcc -shared list-of-files -lc -Wl,-soname -Wl,libfoo.so.0 -o .libs/libfoo.so.0.0.0 The resulting link command is missing "-Wl,--rpath -Wl,/prefix/lib" options (example using Gnu ld).Please rerun above command with `./libtool --debug' and post the output, packed (bzip2 or gzip preferred); also `./libtool --debug'.
Ok, here's the real example. Using Sun ld as linker.Two attachments included. libtool-debug.tar.gz is the debug output. libtool-nodebug.txt is short non-debug output from the build+install with some "ldd" and "dump -Lv" commands showing how Sun dynamic linker fails to find libgcc_s.so during runtime because the libb.so library is missing RPATH (the "a" executable itself has it, but it is irrelevant on Solaris).
---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
libtool-nodebug.txt
Description: Non-debug output
libtool-debug.tar.gz
Description: Debug output, one command per file
[Prev in Thread] | Current Thread | [Next in Thread] |