> From: Dan Fandrich <dan_at_coneharvesters.com>
> Date: Sat, 14 Feb 2009 00:47:20 -0800
> On Fri, Feb 13, 2009 at 03:21:44PM +0000, Jamie Lokier wrote:
> > I say it's probably a libtool bug, however because of the side
> effects
> > of loading a shared lib at run time, at least the libtool behaviour
> > gives consistent run time behaviour between static and shared
> builds.
> > It's rarely what you wanted, though.
>
> Sounds like a bug to me, too. If "libtool --config | grep
> link_all_deplibs"
> gives "unknown", then libtool isn't detecting this properly.
>
link_all_deplibs=yes on Mac OS X. But then the same is true for all
platforms by default. Some distros (I know Debian does this) patch it
to use link_all_deplibs=no, but libtool upstream doesn't recommend
doing this because of the problems with static libs, cross-compiling
and linking to non-installed libs. I guess this could be considered a
libtool bug, but it's deep in the heart of libtool and unlikely to
change soon.

I just thought adding the linker flag would be an easy way to slim
down curl/libcurl whatever libtool does, but it isn't a big deal.
Maybe this isn't an issue on other platforms and is only of interest
on OS X, so I can just add it to my packages. I also --disable-static
and manually clean dependency_libs from libcurl.la so that no
unnecessary linking goes on.

Daniel
Received on 2009-02-15