From: Albert Chin <gcc@lists.thewrittenword.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Richard Henderson <rth@redhat.com>,
Bryce McKinlay <bryce@waitaki.otago.ac.nz>,
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: Wed, 27 Feb 2002 20:17:00 -0000 [thread overview]
Message-ID: <20020227215433.D46093@oolong.il.thewrittenword.com> (raw)
In-Reply-To: <orzo1ucqjn.fsf@free.redhat.lsd.ic.unicamp.br>; from aoliva@redhat.com on Wed, Feb 27, 2002 at 11:02:04PM -0300
On Wed, Feb 27, 2002 at 11:02:04PM -0300, Alexandre Oliva wrote:
> On Feb 25, 2002, Richard Henderson <rth@redhat.com> wrote:
>
> > At present I believe the answer to the first question is "one".
> > You are the only person I'm aware of that works on gcc that knows
> > how to figure out what's happening when something goes wrong with
> > libtool. Note that this is immaterial to whether or not it is
> > libtool that is at fault -- one must still track down the cause,
> > which means understanding how libtool works.
>
> I agree. This is a problem. There are 3 ways to fix it:
>
> - getting more people to understand libtool :-)
>
> - giving up on libtool and duplicating it poorly, probably running
> into the security problems I mentioned above
>
> - getting some people to reimplement (relevant parts of) libtool for
> GCC such that we no longer depend on a single person
Have the libtool issues been directed to the libtool mailing list
where others are watching? Would be nice if GCC used a more recent
version of libtool from CVS.
--
albert chin (china@thewrittenword.com)
next prev parent reply other threads:[~2002-02-28 3:54 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
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 [this message]
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=20020227215433.D46093@oolong.il.thewrittenword.com \
--to=gcc@lists.thewrittenword.com \
--cc=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 \
--cc=rth@redhat.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).