From: John Marino <binutils@marino.st>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Cc: Mike Frysinger <vapier@gentoo.org>, binutils@sourceware.org
Subject: Re: PATCH: Fix support for DragonFly BSD on binutils 2.21 and trunk
Date: Tue, 08 Mar 2011 19:50:00 -0000 [thread overview]
Message-ID: <4D768774.8090507@marino.st> (raw)
In-Reply-To: <20110308194253.GD30822@gmx.de>
Ralf Wildenhues wrote:
> Hello,
>
> * MFL Commissioner wrote on Tue, Mar 08, 2011 at 08:35:26PM CET:
>> I'm a little confused about this. It appears binutils/config.guess
>> is getting updated independently (iow not tracking the master
>> version).
>
> I think I just forgot to copy the whole file over last time, and instead
> only synced the latest change, thinking that the files would be
> identical otherwise.
>
> I'm fine with updating the file from the gnulib master copy, but please
> in sync with GCC, and let's give em the (hopefully very short) time now
> to branch, so this doesn't interfere.
>
> Thanks,
> Ralf
Hi Ralf,
I didn't quite follow that.
Did you say you want to wait until gcc trunk branches to 4.6 before
updating config.guess on both gcc and binutils simultaneously?
Wouldn't people want the very latest config.guess in place before
branching? I'm primarily concerned with getting binutils 2.51 fixed
before it's next release (I saw it went into beta today?)
John
next prev parent reply other threads:[~2011-03-08 19:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 18:14 John Marino
2011-03-08 18:25 ` Mike Frysinger
2011-03-08 18:42 ` John Marino
2011-03-08 19:11 ` Mike Frysinger
2011-03-08 18:54 ` Mike Frysinger
2011-03-08 18:58 ` John Marino
2011-03-08 19:09 ` Mike Frysinger
2011-03-08 19:30 ` John Marino
2011-03-08 19:39 ` MFL Commissioner
2011-03-08 19:43 ` Ralf Wildenhues
2011-03-08 19:50 ` John Marino [this message]
2011-03-08 20:01 ` Ralf Wildenhues
2011-03-08 20:09 ` John Marino
2011-03-08 20:16 ` Ralf Wildenhues
2011-03-08 20:16 ` Mike Frysinger
2011-03-08 20:10 ` Mike Frysinger
2011-03-08 20:15 ` John Marino
2011-03-08 20:21 ` Mike Frysinger
2011-03-08 19:51 ` Mike Frysinger
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=4D768774.8090507@marino.st \
--to=binutils@marino.st \
--cc=Ralf.Wildenhues@gmx.de \
--cc=binutils@sourceware.org \
--cc=vapier@gentoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).