Re: Fixing *other* libtool problem?
"Marcelo E. Magallon" <mmagallo@efis.ucr.ac.cr> writes:
> Try adding -lc to whatever_LA_LDADD in the Makefile.am's
That was the first thing I tried, but it didn't seem to work. The -lc
would show up in the call to libtool (and the libtool info pages even
imply that using -lxxx is the right way to get dependencies into
libs), but libtool strips the -lc from the call to gcc -shared...
> As Shaleh pointed out, if you libtoolize --force --copy, the Debian
> modified ltmain.sh and something-else-I-can't-recall will be copied,
> but that *may* get you into trouble if the upstream author uses
> libtool 1.2 (which wasn't available in slink last time I checked). I
> will also make the patch *very* big and sometimes hard to manage
> (applying it to new upstream releases will likely fail -- I spend a
> few minutes getting the patches back in from time to time in some of
> my packages that use libtool)
That's kind of a pain, but I'll try it if nothing else works.
--
Rob Browning <rlb@cs.utexas.edu> PGP=E80E0D04F521A094 532B97F5D64E3930
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: