[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
stuff to do: fix libtool
- To: tech_(_at_)_openbsd_(_dot_)_org
- Subject: stuff to do: fix libtool
- From: Marc Espie <espie_(_at_)_nerim_(_dot_)_net>
- Date: Fri, 17 Dec 2004 20:31:08 +0100
- Mail-followup-to: tech_(_at_)_openbsd_(_dot_)_org
- Reply-to: espie_(_at_)_nerim_(_dot_)_net
The libtool(s) we have in the ports tree don't do things right for us.
If (say) you use gcc -L/usr/local/lib, and you link with
.libs/libfoo.la, then libtool will arrange stuff so that you get
gcc -L/usr/local/lib -L.libs -lfoo
The issue is that, if there is a libfoo under /usr/local/lib, you link
with THAT one instead of the one you've just built.
It should be possible to teach libtool that, when it sees .libs/libfoo.la
on a link line, the -L.libs option should migrate up in front of
I know I can do it, I just don't have the time to dive into libtool again,
and frankly, I'm a bit tired.
If someone feels like tackling a huge pile of rotting shell, find out what
needs to be changed, and produce a small patch, that would be VERY nice.