From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Daniel Jacobowitz <drow@false.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 16:14:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64N.0702091554020.1045@blysk.ds.pg.gda.pl> (raw)
In-Reply-To: <20070209153841.GA12038@nevyn.them.org>
On Fri, 9 Feb 2007, Daniel Jacobowitz wrote:
> > Could using autoconf 2.61 have helped?
>
> Yes, but I am unwilling to try migrating more than one thing at a time
> right now. This patch puts all of gcc and src, at long last, on the
> same version of autoconf. Moving the whole tree to 2.61 is a separate
> project.
I see, though frankly I wouldn't consider switching from 2.59 to 2.61 too
much of a project. And certainly much less than doing the 2.13 to 2.59
conversion at the top level. Of course in 2.61 there may be different
bugs than in 2.59, but I gather the new version is not meant to imply any
kind of revolution. Even if there were some subtle problems somewhere,
they should get sorted out as things go by stage 3.
Or is it because of the new structure of install directories?
Maciej
next prev parent reply other threads:[~2007-02-09 16:14 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 [this message]
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
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=Pine.LNX.4.64N.0702091554020.1045@blysk.ds.pg.gda.pl \
--to=macro@linux-mips.org \
--cc=binutils@sourceware.org \
--cc=dj@redhat.com \
--cc=drow@false.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.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