From: Alexandre Oliva <aoliva@redhat.com>
To: Steve Ellcey <sje@cup.hp.com>
Cc: dmj+@andrew.cmu.edu, binutils@sources.redhat.com
Subject: Re: libtool changes for HP-UX IA64 support
Date: Tue, 22 Jan 2002 18:03:00 -0000 [thread overview]
Message-ID: <orsn8xrgu1.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: Steve Ellcey's message of "Tue, 22 Jan 2002 16:07:56 -0800 (PST)"
On Jan 22, 2002, Steve Ellcey <sje@cup.hp.com> wrote:
> Since it doesn't look like we will be able to update libtool in binutils
> for the 2.12 release, I have created a patch for the libtool that is
> checked in to binutils. I am hoping someone can review it and check it
> in.
I have reviewed the patch, and it looks quite reasonable to me, but
I'll defer the decision on checking it in to the release manager.
If it's not asking for too much, I'd appreciate to have chunks of code
that are not in the original libtool snapshot enclosed in # GCC LOCAL
comments, like other similar changes that have already been
installed. Would you please make this change?
After this patch goes in, every configure script in directories that
use libtool must be rebuilt, such that it gets the changes to
libtool.m4.
Thanks, and sorry for consistently dropping the ball in this regard
:-(
--
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 *Please* write to mailing lists, not to me
next prev parent reply other threads:[~2002-01-23 1:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-22 16:44 Steve Ellcey
2002-01-22 18:03 ` Alexandre Oliva [this message]
2002-01-23 3:06 ` Daniel Jacobowitz
2002-01-27 20:39 ` Daniel Jacobowitz
2002-01-27 21:00 ` Alexandre Oliva
2002-01-27 22:11 ` Daniel Jacobowitz
2002-01-27 23:10 ` Daniel Jacobowitz
2002-01-28 1:55 ` Alexandre Oliva
2002-01-23 9:54 Steve Ellcey
2002-01-23 10:59 ` 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=orsn8xrgu1.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=dmj+@andrew.cmu.edu \
--cc=sje@cup.hp.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).