From: Tristan Gingold <gingold@adacore.com>
To: Allan McRae <allan@archlinux.org>
Cc: Tristan Gingold <gingold@act-europe.fr>, binutils@sourceware.org
Subject: Re: binutils-2.23.90 snapshot is available
Date: Mon, 23 Sep 2013 08:46:00 -0000 [thread overview]
Message-ID: <46592EB0-2BF4-4E18-8EA3-B7B4610512B2@adacore.com> (raw)
In-Reply-To: <523C3728.1000008@archlinux.org>
On Sep 20, 2013, at 1:53 PM, Allan McRae <allan@archlinux.org> wrote:
> On 20/09/13 18:28, Tristan Gingold wrote:
>> Hi,
>>
>> I have just uploaded prerelease 2.23.90 for binutils 2.24 at:
>> ftp://sourceware.org/pub/binutils/snapshots/binutils-2.23.90.tar.bz2
>>
>> b278da68838a5548e671ad835576a8fe binutils-2.23.90.tar.bz2
>>
>> This snapshot was sanity-checked for i686-pc-linux-gnu
>> Please test it for your favorite hosts/targets.
>>
>> Tristan.
>
> I see one new failure on Arch Linux x86_64-unknown-linux-gnu:
> FAIL: objcopy on compressed debug sections
>
> This happened since I last built from binutils trunk at the start of August.
>
>
> Other than that, I see the two failures that have been present in the
> last release too.
>
> x86_64-unknown-linux-gnu:
> FAIL: exception_static_test
> (https://sourceware.org/bugzilla/show_bug.cgi?id=15407)
>
> i686-pc-linux-gnu:
> FAIL: debug_msg.sh
> (https://sourceware.org/bugzilla/show_bug.cgi?id=15411)
Thank you for the tests.
Tristan.
next prev parent reply other threads:[~2013-09-23 8:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 8:28 Tristan Gingold
2013-09-20 11:53 ` Allan McRae
2013-09-21 0:16 ` Allan McRae
2013-09-27 18:08 ` H.J. Lu
2013-10-09 16:08 ` H.J. Lu
2013-10-12 17:01 ` H.J. Lu
2013-09-23 8:46 ` Tristan Gingold [this message]
2013-09-20 12:11 ` Alan Modra
2013-09-20 12:15 ` Tristan Gingold
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=46592EB0-2BF4-4E18-8EA3-B7B4610512B2@adacore.com \
--to=gingold@adacore.com \
--cc=allan@archlinux.org \
--cc=binutils@sourceware.org \
--cc=gingold@act-europe.fr \
/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).