> > On Nov 8, 2012 6:38 PM, "Poor Yorick" <org.gnu.lists.libt...@pooryorick.com> [SNIP] > > the culprit turns out to be "/path/to/software/collection/lib/libffi.la", > which was included in "dependency_libs" of > /path/to/src/glib-2.32.4/glib-2.32.4/gobject/libgobject-2.0.la. If I remove > that, the error disappears. > > Here's a libtool command > (pwd=/path/to/src/glib-2.32.4/glib-2.32.4/gobject/libgobject/tests) that > creates a wrapper with the bad LD_LIBRARY_PATH: > > ../../libtool --tag=CC --mode=link gcc -m64 -g -O2 -Wall > -L/path/to/src/glib-2.32.4/glib-2.32.4/glib/.libs -o boxed boxed.o > ../libgobject-2.0.la ../../gthread/libgthread-2.0.la ../../glib/libglib-2.0.la > > Now the question is how to systematically work around such problems? Editing > any of the .la files doesn't seem right. Is there something I can add to my > build environment or configuration options? >
I tried various things to try to get libtool to do the right thing, but finally just made a symylink to libffi /path/to/src/glib-2.32.4/glib-2.32.4/glib/.libs, which convinced libtool not to add /path/to/software/collection/lib to the LD_LIBRARY_PATH in the wrappers scripts. I wish I could have found a less ughly hack, or even a good fix. Ref: http://bugzilla.gnome.org/show_bug.cgi?id=688054 -- Yorick _______________________________________________ https://lists.gnu.org/mailman/listinfo/libtool
