automake and custom rpath

Question

I have to ship a third-party library with an application. Because I don't want to set LD_LIBRARY_PATH by hand or require any wrapper script I want automake to set a custom rpath. Unfortunately libtool has its own -rpath option and adding -Wl,-rpath,/foo/bar to LDFLAGS only results in

g++: unrecognized option '-rpath'

because libtool seems to get confused with the command line options. The same happens with the alternative form -Wl,-rpath -Wl,/foo/bar.

Is there any way to specify a custom rpath without libtool interference?

score 2 · Accepted Answer · answered Oct 06 '12 at 09:25

2

As you said, libtool has its own -rpath option. Any reason you don't want to use it?

% libtool link g++ foo.cc -o foo -rpath /somewhere
libtool: link: g++ foo.cc -o foo  -Wl,-rpath -Wl,/somewhere
% readelf -d foo | grep RPATH
0x000000000000000f (RPATH)              Library rpath: [/somewhere]

None of the examples in the Automake or Libtool manuals use -Wl to specify -rpath.

answered Oct 06 '12 at 09:25

adl

15,627
6
51
65

Thanks, specifying `-rpath` (or `-R`) in `_LDFLAGS` works. Still seems weird that libtool only accepts a random mix of standard and own (linker) flags. – scai Oct 08 '12 at 08:25
Can I specify relative `rpath`? Libtool fails with error saying: `error: only absolute run-paths are allowed` – Vadim Kotov Oct 12 '17 at 14:40
1

I mean, I'd like to use '$$ORIGIN/libs` – Vadim Kotov Oct 12 '17 at 15:11

automake and custom rpath

1 Answers1

Linked