What's the current status of libtool support for $ORIGIN? The docs don't mention it. In the list I find: http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=%24ORIGIN&submit=Search%21&idxname=libto
What's the current status of libtool support for $ORIGIN? The docs don't mention it. In the list I find: http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=%24ORIGIN&submit=Search%21&idxname=libto
[...] Yes, relative paths here are resolved against current directory, not the library location. But you can use $ORIGIN here, it is expanded to the library location by dynamic linker: -Wl,-rpath,\$O
Hello Ethan, * Ethan Mallove wrote on Fri, Feb 20, 2009 at 10:14:13PM CET: Yep. Sorry, but Libtool doesn't support $ORIGIN yet. Currently, the best bet for relocatable packages with Libtool is using
Hi, I am using the run-time linker $ORIGIN variable with Libtool in an apparently unsupported way to create relocatable objects. After Libtool generates a "libtool" script, I am commenting out the be
Hi Brian, * Brian Lu wrote on Mon, Mar 20, 2006 at 11:05:26AM CET: Right. Libtool is missing several bits to be able to properly support such relocatable installations. One issue is that the installe
Hi, experts, I need to build Ekiga on solaris, which uses libtool to do the compiling and linking I need to set '$ORIGIN' in final executable RUNPATH. So user can install Ekiga anywhere he likes. I u
Hi Cristoph, * Christoph Bartoschek wrote on Sun, Jun 05, 2005 at 06:17:13PM CEST: *snip typical cross compilation situation* One Right Way[tm] would be to add some kind of DESTDIR support for link t
Hi, On Solaris and Linux platforms the $ORIGIN variable as RPATH is supported and is working. For AIX '$ORIGIN/../lib' is part of the '-blibpath:' option and after compiling and linking, Using objdum
The "relative hardcoded runpaths" aren't supported by all systems, so adding support for it to Libtool wouldn't be useful to those of us who use such systems. It has been requested 1000 times, but it
Hi, will libtool support in the future "relative hardcoded runpaths" ? This allow us to move installed "bin/*" and "lib/*" without modification. Or assume you install binary packages and are ask just
Howdy, I'm having trouble building libtool on my solaris 2.8 system. I'm enclosing the complete build log below. Could you take a peek and let me know what I"m doing wrong please? Regards and thanks
I believe libtool supports both -Wl, and -Xlinker, and translates it to -Wl, if it runs the compiler driver. IIRC, libtool requires -R arguments to be a full pathname. Now, what would be really great
In this case you'd be passing -R LIBDIR to libtool, not the linker or compiler, and libtool would translate it into the linker-specific option, when one is available. (The snippet above is from the L
I know about the -Wl flag. I some how got the idea that -Xlinker is a libtool flag which will use the appropriate option to pass it to the linker, I don't where I got that idea - it's obviously a gc
Ganesan: I think you can get the exact same result by using the -Wl,-Bsymbolic flag. It will be recognized by Libtool, and passed to the linker. -Xlinker is a gcc equivalent to -Wl, so if I recall co
Hi, I am currently using -Bsymbolic to compile my libraries. I pass in the flag using "-Xlinker -Bsymbolic". Is "-Bsymbolic" portable and if it is can the flag be added to libtool directly. Linux, Fr
Hmm, that's correct. We do pass in the install location of a library using -rpath, may be we can a similar flag for a program. This is very convenient for relocatable packages. I am not sure if it's
This would require libtool to know the directory in which a program is going to be installed. This information isn't available when the program is linked. -- Alexandre Oliva Enjoy Guarana', see http:
I would like to add an RPATH with $ORIGIN (supported on Solaris and GLIBC platforms), but libtool complains that an absolute path is needed. A following trivial fix to ltmain.in fixes the problem. Th