public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Bryce McKinlay <bryce@waitaki.otago.ac.nz>
Cc: Phil Edwards <phil@jaj.com>,
	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 21:22:00 -0000	[thread overview]
Message-ID: <orit8m43ft.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: Bryce McKinlay's message of "Mon, 25 Feb 2002 16:44:44 +1300"

On Feb 25, 2002, Bryce McKinlay <bryce@waitaki.otago.ac.nz> wrote:

> Alexandre Oliva wrote:
>>> frankly, the platforms on which libtool is supposed to be magically
>>> helpful are platforms which IMHO need to die, and the sooner we
>>> abandon them the better.
>>> 
>> 
>> Yay!  HP-UX, AIX, Solaris, Windows, no more!

> Are you saying that "gcc -shared" does not currently work on these
> platforms?

Nope.  I'm saying that there's a bit more than gcc -shared.  There are
library naming conventions.  There are versioning mechanisms that vary
from system to system.  There are options to get libraries to find one
another at run time.  There are a lot of small details that, when
added up, may turn into enough of a hassle that a lot of libtool's
built-in intelligence ends up having to be duplicated, and poorly.

The only advantage I see for GCC in keep on using libtool is the
abstraction.  Abstraction comes with a price, though: it becomes
harder to peek into the implementation details.  But do people really
want to do it?  How many of the problems that were blamed on libtool
were really bugs in libtool?  How many times we didn't have problems
just because we were using this package?  Is it really worth to ditch
it in favor of a more limited solution that will require effort to put
in place and maintain?  I'm not sure.

As I wrote before, I don't oppose this move.  But it shouldn't be
taken lightly either.  There may be some (or a lot) to gain, but I'm
pretty sure there's a lot to lose.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer

  reply	other threads:[~2002-02-25  3:59 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 [this message]
2002-02-24 22:05             ` Jeff Sturm
2002-02-24 22:17               ` Phil Edwards
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=orit8m43ft.fsf@free.redhat.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=bryce@waitaki.otago.ac.nz \
    --cc=gcc@gcc.gnu.org \
    --cc=java@gcc.gnu.org \
    --cc=nferrier@tapsellferrier.co.uk \
    --cc=phil@jaj.com \
    /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).