From: Steve Ellcey <sje@cup.hp.com>
To: macro@linux-mips.org, drow@false.org, dj@redhat.com
Cc: gcc-patches@gcc.gnu.org, binutils@sourceware.org,
gdb-patches@sourceware.org, newlib@sourceware.org
Subject: Re: Updating top-level autoconf to 2.59
Date: Fri, 09 Feb 2007 17:48:00 -0000 [thread overview]
Message-ID: <200702091747.JAA28249@hpsje.cup.hp.com> (raw)
In-Reply-To: <Pine.LNX.4.64N.0702091717250.1045@blysk.ds.pg.gda.pl>
> BTW, do we still want to carry local copies of severely obsolete libtool
> scripts? I have had success with libtool 1.5.22 and GCC 4.1.1 after a
> moderate amount of work (mostly shuffling bits around; libjava/ was the
> most involving part) -- if there is interest in upgrading (which might
> help some people with less common configurations) I could port them to the
> trunk sooner rather than later.
>
> Maciej
Actually, getting libtool updated was my original goal in all of this.
I was told that we couldn't update libtool until we had updated
autoconf. So now that autoconf is updated, I hope we can work on
libtool.
Steve Ellcey
sje@cup.hp.com
next prev parent reply other threads:[~2007-02-09 17:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070111225346.GA1335@nevyn.them.org>
[not found] ` <20070207193352.GA13757@nevyn.them.org>
[not found] ` <xnr6t1hdvt.fsf@greed.delorie.com>
2007-02-08 22:20 ` Daniel Jacobowitz
2007-02-08 22:30 ` DJ Delorie
2007-02-08 22:38 ` Daniel Jacobowitz
2007-02-08 22:44 ` DJ Delorie
2007-02-08 22:54 ` DJ Delorie
2007-02-09 15:16 ` Daniel Jacobowitz
2007-02-09 15:37 ` Maciej W. Rozycki
2007-02-09 15:39 ` Daniel Jacobowitz
2007-02-09 16:14 ` Maciej W. Rozycki
2007-02-09 16:17 ` Daniel Jacobowitz
2007-02-09 16:33 ` Andreas Schwab
2007-02-09 17:39 ` Maciej W. Rozycki
2007-02-09 17:42 ` Daniel Jacobowitz
2007-02-09 17:53 ` Maciej W. Rozycki
2007-02-09 17:48 ` Steve Ellcey [this message]
2007-02-09 20:45 ` Tom Tromey
2007-02-13 9:25 ` Maciej W. Rozycki
2007-02-13 10:30 ` Andreas Schwab
2007-02-09 16:29 ` Joseph S. Myers
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=200702091747.JAA28249@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=binutils@sourceware.org \
--cc=dj@redhat.com \
--cc=drow@false.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.org \
--cc=newlib@sourceware.org \
/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