[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Non-standard link paths
From: |
Bill Moseley |
Subject: |
Non-standard link paths |
Date: |
Thu, 29 Jan 2004 07:31:32 -0800 |
User-agent: |
Mutt/1.5.4i |
We are always struggling with linking with (run-time) libraries
installed in non-standard locations.
Is it true now that with autoconf the way to do this is:
./configure \
CPPFLAGS=-I/path/to/headers \
LDFLAGS='-R/path/to/lib -L/path-to/lib'
and that avoids the need for LD_RUN_PATH? I get confused because I
install some packages using old versions of autoconf and need to use
LD_RUN_PATH before building/linking.
How portable is the above? Does autoconf also deal with platforms where
LD_RUN_PATH is not supported? I believe IRIX doesn't support
LD_RUN_PATH.
And to clear up something else, is it correct that using
--with-foo=/path/to/foo
is not recommended -- rather the recommended way is simply --with-foo
and use CPPFLAGS and LDFLAGS.
Thanks,
BTW --- this question was prompted by this list message:
http://swish-e.org/Discussion/archive/2004-01/6925.html
which describes what they went through to build on IRIX and Solaris.
Looks like more work than needed, but that's always the case when
learning. I would love to get feedback on that message from someone
here that understand this stuff much better than I do.
--
Bill Moseley
address@hidden
- Non-standard link paths,
Bill Moseley <=