LibTiff Mailing List
TIFF and LibTiff Mailing List Archive
April 2008
Previous Thread
Next Thread
Previous by Thread
Next by Thread
Previous by Date
Next by Date
Contact
The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems
Thread
2008.04.10 23:57 "Re: Linking against libz, libjpeg", by Bob Friesenhahn
On Thu, 10 Apr 2008, Dean wrote: >>> Note that I tell it to look for zlib and jpeg in /usr/dist/share/..., >>> but the >>> compiled binaries link against /usr/lib: What evidence are you using to know that the compiled binaries link against /usr/lib? If you are using 'ldd' to test which libraries are used, then it is important to know that on Solaris, the 'crle' command is used to set the default linker run-time search path (similar to ldconfig on Linux and FreeBSD). Unless a -R option was included in your build to hard-code the run-time search path for the library, the system's version may use a name similar enough that it will be used by default since it is in the linker run path and your library is not. If each library is installed in its own directory tree, then you should include a hard-coded run path. It looks like libtiff's configure accepts a '--enable-rpath' to automatically add a run-path at link time. Do 'man ld.so.1' to learn about the run-time linker. Here is some sample output from crle: % crle Configuration file [version 4]: /var/ld/ld.config Default Library Path (ELF): /lib:/usr/lib:/usr/openwin/lib:/usr/local/lib:/usr/sfw/lib Trusted Directories (ELF): /lib/secure:/usr/lib/secure (system default) Command line: crle -c /var/ld/ld.config -l /lib:/usr/lib:/usr/openwin/lib:/usr/local/lib:/usr/sfw/lib ====================================== Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/