public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Phil Edwards <phil@jaj.com>
Cc: Jeff Sturm <jsturm@one-point.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: Mon, 25 Feb 2002 05:36:00 -0000	[thread overview]
Message-ID: <orpu2ty9cn.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: Phil Edwards's message of "Mon, 25 Feb 2002 01:23:56 -0500"

On Feb 25, 2002, Phil Edwards <phil@jaj.com> wrote:

> On Mon, Feb 25, 2002 at 03:17:02AM -0300, Alexandre Oliva wrote:
>> On Feb 25, 2002, Phil Edwards <phil@jaj.com> wrote:
>> 
>> > I agree here; it seems we spend more time undoing libtool's abstraction
>> > than libtool spends adding it.  :-)
>> 
>> Do you really mean this?  I'd like to know of such situations, in
>> which you had to undo libtool's abstraction.  That's pretty sad.

> Mainly I'm referring to the current situation.

Aha!  So, it turns out that the current situation had nothing at all
to do with libtool.  The whole issue was on how to pass -shared-libgcc
to the link command issued by libtool, and the implications of doing
so for other systems.

Ok, I'll give you that libtool made this non-optimal by requiring such
flag to already be present at its configuration time, which is what
confused RTH.  IMO, this may be addressed in future releases of
libtool.  But hey! if this is all you have to count in as `undoing
libtool's abstraction', then it seems that you're pretty satisfied
with it :-)

-- 
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 13:34 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
2002-02-24 22:24                 ` Alexandre Oliva
2002-02-24 23:20                   ` Phil Edwards
2002-02-25  5:36                     ` Alexandre Oliva [this message]
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=orpu2ty9cn.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=jsturm@one-point.com \
    --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).