From: Phil Edwards <phil@jaj.com>
To: Jeff Sturm <jsturm@one-point.com>
Cc: Alexandre Oliva <aoliva@redhat.com>,
Bryce McKinlay <bryce@waitaki.otago.ac.nz>,
Nic Ferrier <nferrier@tapsellferrier.co.uk>,
java@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: Get rid of libtool? [was Re: Makefile problems]
Date: Sun, 24 Feb 2002 22:17:00 -0000 [thread overview]
Message-ID: <20020225010454.A27334@disaster.basement.lan> (raw)
In-Reply-To: <Pine.LNX.4.10.10202250019250.26667-100000@mars.deadcafe.org>; from jsturm@one-point.com on Mon, Feb 25, 2002 at 12:45:11AM -0500
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. :-)
Phil
--
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
next prev parent reply other threads:[~2002-02-25 6:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C78B3B6.5000303@waitaki.otago.ac.nz>
[not found] ` <87it8mbse7.fsf@tf1.tapsellferrier.co.uk>
2002-02-24 16:21 ` Bryce McKinlay
2002-02-24 19:16 ` Brian Jones
2002-02-24 19:35 ` Phil Edwards
2002-02-24 19:45 ` Alexandre Oliva
2002-02-24 19:59 ` Bryce McKinlay
2002-02-24 21:22 ` Alexandre Oliva
2002-02-24 22:05 ` Jeff Sturm
2002-02-24 22:17 ` Phil Edwards [this message]
2002-02-24 22:24 ` Alexandre Oliva
2002-02-24 23:20 ` Phil Edwards
2002-02-25 5:36 ` Alexandre Oliva
2002-02-25 9:10 ` Alexandre Oliva
2002-02-26 18:41 ` Jeff Sturm
2002-02-26 18:47 ` Richard Henderson
[not found] ` <3C7C4E67.6050001@waitaki.otago.ac.nz>
2002-02-27 2:41 ` Richard Henderson
2002-02-27 17:55 ` Alexandre Oliva
2002-02-25 16:56 ` Richard Henderson
2002-02-25 17:00 ` Richard Henderson
2002-02-27 18:06 ` Alexandre Oliva
2002-02-27 20:17 ` Albert Chin
2002-02-28 0:02 ` Marc Espie
2002-02-28 0:49 ` Alexandre Oliva
2002-02-28 17:35 ` Phil Edwards
2002-07-03 15:41 Nathanael Nerode
2002-12-28 5:08 ` Alexandre Oliva
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020225010454.A27334@disaster.basement.lan \
--to=phil@jaj.com \
--cc=aoliva@redhat.com \
--cc=bryce@waitaki.otago.ac.nz \
--cc=gcc@gcc.gnu.org \
--cc=java@gcc.gnu.org \
--cc=jsturm@one-point.com \
--cc=nferrier@tapsellferrier.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).