From: Daniel Jacobowitz <drow@false.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: DJ Delorie <dj@redhat.com>,
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:42:00 -0000 [thread overview]
Message-ID: <20070209174229.GA18533@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.64N.0702091717250.1045@blysk.ds.pg.gda.pl>
On Fri, Feb 09, 2007 at 05:39:27PM +0000, Maciej W. Rozycki wrote:
> Sure -- I use a script like this for regenerating all the scripts:
That's not what I meant. There's just too many cases that need to be
tested. Anyway, you're welcome to do it now that the top level has
moved up :-) I'm out of time for the moment.
> 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.
I believe the plan was to upgrade top level configure first, then
libtool and automake (I don't remember if they were supposed to be done
together or in a particular order). Definitely I want to remove the
libtool fork. But talk about a change needing a lot of testing...
Your patches would definitely be welcome.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-02-09 17:42 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 [this message]
2007-02-09 17:53 ` Maciej W. Rozycki
2007-02-09 17:48 ` Steve Ellcey
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=20070209174229.GA18533@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sourceware.org \
--cc=dj@redhat.com \
--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