Bruce Korb wrote:
But this answer belongs in the other thread since it is not related to
the question in this thread (which was how to set some arbitrary
environment variable automatically in the libtool wrapper script).
There isn't such a thing. If you fully link, then you don't need
the "LD
Bruce Korb wrote:
make LDFLAGS=-static
You'll get a real binary, but statically incorporate libraries from the
build tree.
I guess this can be used for my question about LD_LIBRARY_PATH although
it seems this problem will show up for lots of folks. Could this just
be a problem with incorrec
make LDFLAGS=-static
You'll get a real binary, but statically incorporate libraries from the
build tree.
___
http://lists.gnu.org/mailman/listinfo/libtool
Hello,
I have a problem with the LD_LIBRARY_PATH handling inside of the libtool
wrapper. I see a line like:
# Add our own library path to LD_LIBRARY_PATH
LD_LIBRARY_PATH="/usr/pkg/lib:/home/dan/src/myprog/libmine/.libs:$LD_LIBRARY_PATH"
in /home/dan/src/myprog/src/myprog which is the libtool
Hello,
I helped out with a a build system and switching to libtool for a shared
library and am now having the following problem. After building but
before installing, the program used to be able to be tested by
cd foo-x.y/src
./myprog
Unfortunately, myprog was keying off of the directory pa
