This is the mail archive of the
mailing list for the GCC project.
Re: Get rid of libtool? [was Re: Makefile problems]
- From: Phil Edwards <phil at jaj dot com>
- To: Jeff Sturm <jsturm at one-point dot com>
- Cc: Alexandre Oliva <aoliva at redhat dot com>, Bryce McKinlay <bryce at waitaki dot otago dot ac dot nz>, Nic Ferrier <nferrier at tapsellferrier dot co dot uk>, java at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- Date: Mon, 25 Feb 2002 01:04:54 -0500
- Subject: Re: Get rid of libtool? [was Re: Makefile problems]
- References: <email@example.com> <Pine.LNX.firstname.lastname@example.org>
On Mon, Feb 25, 2002 at 12:45:11AM -0500, Jeff Sturm wrote:
> On 25 Feb 2002, Alexandre Oliva wrote:
> > The only advantage I see for GCC in keep on using libtool is the
> > abstraction.
> But when we need a great deal of control over how the shared lib is built
> we have to get past the abstraction layer anyway.
> For any casual, naive attempts to build a shared lib I would
> wholeheartedly recommend libtool. For specific use like libgcj (and
> probably libstdc++) it is more debateable.
I agree here; it seems we spend more time undoing libtool's abstraction
than libtool spends adding it. :-)
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace. We seek
not your counsel, nor your arms. Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen. - Samuel Adams