From: Tristan Gingold <gingold@adacore.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: binutils@sources.redhat.com
Subject: Re: binutils regressions (Re: binutils-2.18.92 snapshot is available)
Date: Tue, 07 Oct 2008 13:01:00 -0000 [thread overview]
Message-ID: <4664D61F-4616-4108-A174-0FA1A2CB869E@adacore.com> (raw)
In-Reply-To: <48EB3F5B.3040204@ubuntu.com>
On Oct 7, 2008, at 12:52 PM, Matthias Klose wrote:
> Matthias Klose schrieb:
>> Matthias Klose schrieb:
>>> binutils i486, amd64, oa64, powerpc, sparc:
>>> Running /build/buildd/binutils-2.18.92.20081003/binutils/
>>> testsuite/binutils-all/objdump.exp ...
>>> Version /build/buildd/binutils-2.18.92.20081003/builddir-single/
>>> binutils/objdump 2.18.92.20081003
>>> FAIL: objdump -W
>>> Running /build/buildd/binutils-2.18.92.20081003/binutils/
>>> testsuite/binutils-all/readelf.exp ...
>>> Version /build/buildd/binutils-2.18.92.20081003/builddir-single/
>>> binutils/readelf 2.18.92.20081003
>>> FAIL: readelf -wa (compressed)
>>
>> these did start to fail between 20080707 and 20080814.
>
> my mistake. missing build dependency on zlib-dev
That's coherent with my tests as there are no failures on x86 nor ppc.
Good!
prev parent reply other threads:[~2008-10-07 13:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 8:40 binutils-2.18.92 snapshot is available Tristan Gingold
2008-10-02 9:17 ` Andreas Schwab
2008-10-02 9:25 ` Tristan Gingold
2008-10-02 9:28 ` Andreas Schwab
2008-10-02 9:38 ` Tristan Gingold
2008-10-02 9:51 ` Andreas Schwab
2008-10-02 9:57 ` Tristan Gingold
2008-10-02 15:01 ` Nick Clifton
2008-10-03 12:59 ` Tristan Gingold
2008-10-06 13:30 ` Matthias Klose
2008-10-07 8:41 ` Tristan Gingold
2008-10-07 10:28 ` binutils regressions (Re: binutils-2.18.92 snapshot is available) Matthias Klose
2008-10-07 10:52 ` Matthias Klose
2008-10-07 13:01 ` Tristan Gingold [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=4664D61F-4616-4108-A174-0FA1A2CB869E@adacore.com \
--to=gingold@adacore.com \
--cc=binutils@sources.redhat.com \
--cc=doko@ubuntu.com \
/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).