Date: Wed, 02 Sep 1998 19:35:24 +0200 From: Mark Murray <mark@grondar.za> To: John Polstra <jdp@polstra.com> Cc: current@FreeBSD.ORG Subject: B CURRENT Build environment (Was: Re: Why no ldconfig for ELF?) Message-ID: <199809021735.TAA01877@gratis.grondar.za>
next in thread | raw e-mail | index | archive | help
John Polstra wrote in answer to an unrelated question:
> You specify the search path at _link_ time with LD_RUN_PATH or the
> "-R" linker option. The path is saved in the executable or shared
> library itself.
Hmm - this raises questions. I am trying to unravel what happens in
an aout->ELF build and at the same time make BMaked perl5 compile
to ELF on an aout system.
In one of my Makefiles I have:
lib/auto/POSIX/POSIX.so:
LD_RUN_PATH=\"${WORLDTMP}${SHLIBDIR}:${WORLDTMP}/usr/lib\" \
sh ext/util/make_ext dynamic ${.TARGET} \
MAKE=make PERL_SRC=${.OBJDIR}
The line beginning LD_RUN_PATH is the critical bit; I need to pass
the current _build_ directory containing the ELF libraries (this system
is currently a.out). What is the right way to do this? The above does not
work, as ${WORLDTMP} is not set here, only in /usr/src/Makefile.inc1.
How might this break an ELF load later? Will the binary have the wrong
load directories hardcoded?
Thanks!
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809021735.TAA01877>