From: Andreas Schwab <schwab@suse.de>
To: Steve Ellcey <sje@cup.hp.com>
Cc: jjohnstn@redhat.com, bonzini@gnu.org,
libtool@cwilson.fastmail.fm, newlib@sourceware.org,
aoliva@redhat.com, gcc-patches@gcc.gnu.org,
gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: New libtool is in the GCC and Src trees.
Date: Mon, 28 May 2007 13:33:00 -0000 [thread overview]
Message-ID: <je4plxgjir.fsf@sykes.suse.de> (raw)
In-Reply-To: <200705241735.KAA09881@hpsje.cup.hp.com> (Steve Ellcey's message of "Thu\, 24 May 2007 10\:35\:28 -0700 \(PDT\)")
Steve Ellcey <sje@cup.hp.com> writes:
> The GCC and src trees have been updated with the new libtool. Let me
> know if you run into problems.
All the generated aclocal.m4 files contain a copy of an old libtool.m4.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2007-05-28 13:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 17:35 Steve Ellcey
2007-05-24 18:07 ` Steve Ellcey
2007-05-24 18:46 ` Steve Ellcey
2007-05-24 20:02 ` Andreas Tobler
2007-05-24 20:33 ` Steve Ellcey
2007-05-24 21:09 ` Andreas Tobler
2007-05-24 21:14 ` libtool
2007-05-24 22:13 ` Mike Stump
2007-05-25 17:38 ` Andreas Tobler
2007-05-25 17:43 ` Paolo Bonzini
2007-05-25 17:50 ` Eric Christopher
2007-05-25 19:33 ` Andreas Tobler
2007-05-25 19:39 ` Eric Christopher
2007-05-24 20:37 ` Mike Stump
2007-05-25 0:12 ` Andrew Pinski
2007-05-28 12:49 ` Andreas Schwab
2007-05-28 19:07 ` Charles Wilson
2007-05-29 1:25 ` Peter O'Gorman
2007-05-28 13:33 ` Andreas Schwab [this message]
[not found] <m3irah6d45.fsf@fleche.redhat.com>
2007-05-25 18:21 ` Steve Ellcey
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=je4plxgjir.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=aoliva@redhat.com \
--cc=binutils@sourceware.org \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jjohnstn@redhat.com \
--cc=libtool@cwilson.fastmail.fm \
--cc=newlib@sourceware.org \
--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