Hi!
Here /usr/bin/libtool is debian's 1.5.26 and /usr/local/bin/libtool is
hand-compiled v2.2:
[EMAIL PROTECTED]:~$ /usr/bin/libtool --mode=execute echo -L . foo
-L . foo
[EMAIL PROTECTED]:~$ /usr/local/bin/libtool --mode=execute echo -L . foo
-L / /
[EMAIL PROTECTED]:~$
Is this a bug?
If it is not a bug, how should I pass -L flags to tools that I execute
via libtool --mode=execute?
This causes us problems in gnutls since we invoke Guile self tests using
the following Makefile.am snippet:
TESTS_ENVIRONMENT = $(top_builddir)/guile/pre-inst-guile -L $(srcdir)
The pre-inst-guile is generated to contain absolute paths, and one
incarnation of it looks like:
GUILE_LOAD_PATH="/home/jas/src/gnutls/guile/modules:$GUILE_LOAD_PATH"
export GUILE_LOAD_PATH
exec /home/jas/src/gnutls/libtool --mode=execute \
-dlopen "/home/jas/src/gnutls/guile/src/libguile-gnutls-v-1.la" \
-dlopen "/home/jas/src/gnutls/guile/src/libguile-gnutls-extra-v-1.la" \
/usr/bin/guile "$@"
Thus, the command to invoke becomes equivalent to:
$ export GUILE_LOAD_PATH=/home/jas/src/gnutls/guile/modules
$ /home/jas/src/gnutls/libtool --mode=execute -dlopen
"/home/jas/src/gnutls/guile/src/libguile-gnutls-v-1.la" -dlopen
"/home/jas/src/gnutls/guile/src/libguile-gnutls-extra-v-1.la" /usr/bin/guile -L
. openpgp-auth.scm
This has worked fine with libtool v1.5, but libtool v2.2 is confused by
the -L and fails.
Thanks,
/Simon
_______________________________________________
Bug-libtool mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-libtool
