From: Nick Clifton <nickc@redhat.com>
To: Matthias Klose <doko@debian.org>, binutils@sourceware.org
Subject: Re: 2.41 branch approaching
Date: Wed, 28 Jun 2023 11:58:20 +0100 [thread overview]
Message-ID: <a275a842-a379-7dbf-0010-ab024ae47018@redhat.com> (raw)
In-Reply-To: <b0a7ed64-e198-fc31-dffd-1135b4b34fab@debian.org>
Hi Matthias,
> In particular,
>
> x86_64-linux-gnu i686-linux-gnu x86_64-linux-gnux32
> ===================================================
>
> Using /<<PKGBUILDDIR>>/binutils/testsuite/config/default.exp as tool-and-target-specific interfa
> ce file.
> Running /<<PKGBUILDDIR>>/binutils/testsuite/binutils-all/aarch64/aarch64.exp ...
> Running /<<PKGBUILDDIR>>/binutils/testsuite/binutils-all/addr2line.exp ...
> FAIL: addr2line ./builddir-single/binutils/./binutils/testsuite/binutils-all/testprog.c:19
>
> FAIL: addr2line -f option fn
> ./builddir-single/binutils/./binutils/testsuite/binutils-all/testprog.c:13
>
> Version /<<PKGBUILDDIR>>/builddir-single/binutils/objdump 2.40.50.20230625
> FAIL: objdump -S
> FAIL: objdump --source-comment
> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-elf/shared.exp ...
> FAIL: Dump pr21978.so
I am not seeing these failures. Can you tell me how the builds
are configured ?
Maybe the problem is related to the compiler that is being used to
compile the test code ? Perhaps the regexps in the tests need to
be adjusted to allow for discrepancies in compiler behaviour ?
(This is just a guess).
Can you supply the binutils.log file for a failing test run so
that I can take a look ?
Cheers
Nick
next prev parent reply other threads:[~2023-06-28 10:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 9:57 Nick Clifton
2023-06-21 18:29 ` Indu Bhagat
2023-06-26 5:34 ` Matthias Klose
2023-06-28 10:58 ` Nick Clifton [this message]
2023-06-28 15:21 ` Matthias Klose
2023-06-28 15:59 ` Nick Clifton
2023-06-28 16:27 ` Matthias Klose
2023-06-29 9:34 ` Matthias Klose
2023-06-29 11:44 ` Nick Clifton
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=a275a842-a379-7dbf-0010-ab024ae47018@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=doko@debian.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).