From: Hamish M. <ha...@cl...> - 2008-05-18 00:48:42
|
On Sat, May 17, 2008 at 06:32:51PM +0200, Stephane Fillod wrote: > It looks like libhamlib has either to be installed beforehand to be > found, but how can it be when Hamlib is compiled for the first time? > Or maybe we have to revert the revision 1.17 of bindings/Makefile.am, > but MakeMaker would then put back the rpath in, and I can't find a way > to tell perl MakeMaker to NOT set a rpath out of the -L. > > diff -u -p -r1.16 -r1.17 > --- bindings/Makefile.am 15 Jan 2006 14:22:00 -0000 1.16 > +++ bindings/Makefile.am 10 Apr 2006 17:27:42 -0000 1.17 > @@ -24,7 +24,7 @@ Hamlib-pl.mk: $(srcdir)/Makefile.PL > INC="$(INCLUDES)" \ > CC="$(CC)" \ > OBJECT="hamlibperl_wrap.o" VERSION="$(PACKAGE_VERSION)" \ > - LIBS="-L$(top_builddir)/src/.libs -lhamlib" > + LIBS="-lhamlib" That's the linker rather than MakeMaker that is putting the RPATH into the binary, I think. The linker's -rpath-link option may be useful here: it specifies a search path for linking only (not for runtime). ie: > - LIBS="-L$(top_builddir)/src/.libs -lhamlib" > + LIBS="--Wl,-rpath-link,$(top_builddir)/src/.libs -lhamlib" Hamish -- Hamish Moffatt VK3SB <ha...@de...> <ha...@cl...> |