From: Daniel Jacobowitz <drow@false.org>
To: Nick Clifton <nickc@redhat.com>
Cc: Andreas Tobler <toa@pop.agri.ch>,
dj@redhat.com, gcc-patches@gcc.gnu.org,
gdb-patches@sourceware.org
Subject: Re: Renaming mingw64 to mingw* for x86_64 architecure
Date: Tue, 09 Jan 2007 13:45:00 -0000 [thread overview]
Message-ID: <20070109134521.GA16727@nevyn.them.org> (raw)
In-Reply-To: <45A34679.7070405@redhat.com>
On Tue, Jan 09, 2007 at 07:38:33AM +0000, Nick Clifton wrote:
> I always go by the version embedded at the top of the current configure
> file. So in this case I used 2.13. I am expecting this to change at
> some point in the near future though.
Yes indeed. I'm just waiting to make sure there aren't any more
problems with top level libgcc before I change anything else in
the build system, but I have a patch to move the top level to autoconf
2.5x and I will be resubmitting it soon. After that we'll probably
migrate the whole tree up to 2.61 at some point.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-01-09 13:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 18:04 Nick Clifton
2007-01-08 18:38 ` DJ Delorie
2007-01-08 21:00 ` Andreas Tobler
2007-01-09 7:38 ` Nick Clifton
2007-01-09 13:45 ` Daniel Jacobowitz [this message]
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=20070109134521.GA16727@nevyn.them.org \
--to=drow@false.org \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=nickc@redhat.com \
--cc=toa@pop.agri.ch \
/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).