public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: Bryce McKinlay <bryce@waitaki.otago.ac.nz>
Cc: 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 19:35:00 -0000	[thread overview]
Message-ID: <20020224222911.D26234@disaster.basement.lan> (raw)
In-Reply-To: <3C797FAA.9070305@waitaki.otago.ac.nz>; from bryce@waitaki.otago.ac.nz on Mon, Feb 25, 2002 at 01:04:58PM +1300

On Mon, Feb 25, 2002 at 01:04:58PM +1300, Bryce McKinlay wrote:
> 
> I must admit that, after a frustrating afternoon yesterday trying to 
> figure out silly libjava build problems when I really wanted to do 
> productive gcj hacking, I am sympathetic to RTH's recent suggestion that 
> we get rid of libtool (and automake?) and instead make sure that "gcc 
> -shared" knows how to build a shared library on all the platforms that 
> we care about.

I would fight the removal of automake.  It's been awfully darn handy for
maintaining libstdc++.  (Yes, the currently-required version has its problems
with subdirs, but the current automake release seems to have fixed those.)

Libtool is completely opaque to me.  I wouldn't fight its removal, but
I'm not pushing for it either.  I also never use it in any of my own
projects... [maintainer hat OFF] 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.

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

  parent reply	other threads:[~2002-02-25  3:31 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 [this message]
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
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=20020224222911.D26234@disaster.basement.lan \
    --to=phil@jaj.com \
    --cc=bryce@waitaki.otago.ac.nz \
    --cc=gcc@gcc.gnu.org \
    --cc=java@gcc.gnu.org \
    --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).