From: Jeff Law <law@redhat.com>
To: "Maciej W. Rozycki" <macro@wdc.com>, gcc-patches@gcc.gnu.org
Cc: Mike Stump <mikestump@comcast.net>,
Chung-Lin Tang <cltang@codesourcery.com>,
Ian Lance Taylor <iant@golang.org>
Subject: Re: [PATCH v4 1/5] libatomic/test: Fix compilation for build sysroot
Date: Mon, 06 Apr 2020 12:10:13 -0600 [thread overview]
Message-ID: <78cb5a2429cf8b6eb043d86e26a9896214eb6765.camel@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.21.2004031734460.461@redsun52.ssa.fujisawa.hgst.com>
On Sat, 2020-04-04 at 00:00 +0100, Maciej W. Rozycki wrote:
> Fix a problem with the libatomic testsuite using a method to determine
> the compiler to use resulting in the tool being different from one the
> library has been built with, and causing a catastrophic failure from the
> lack of a suitable `--sysroot=' option where the `--with-build-sysroot='
> configuration option has been used to build the compiler resulting in
> the inability to link executables.
>
> Address this problem by providing a DejaGNU configuration file defining
> the compiler to use, via the GCC_UNDER_TEST TCL variable, set from $CC
> by autoconf, which will have all the required options set for the target
> compiler to build executables in the environment configured, removing
> failures like:
>
> .../bin/riscv64-linux-gnu-ld: cannot find crt1.o: No such file or directory
> .../bin/riscv64-linux-gnu-ld: cannot find -lm
> collect2: error: ld returned 1 exit status
> compiler exited with status 1
> FAIL: libatomic.c/atomic-compare-exchange-1.c (test for excess errors)
> Excess errors:
> .../bin/riscv64-linux-gnu-ld: cannot find crt1.o: No such file or directory
> .../bin/riscv64-linux-gnu-ld: cannot find -lm
>
> UNRESOLVED: libatomic.c/atomic-compare-exchange-1.c compilation failed to
> produce executable
>
> and bringing overall test results for the `riscv64-linux-gnu' target
> (here with the `x86_64-linux-gnu' host and RISC-V QEMU in the Linux user
> emulation mode as the target board) from:
>
> === libatomic Summary ===
>
> # of unexpected failures 27
> # of unresolved testcases 27
>
> to:
>
> === libatomic Summary ===
>
> # of expected passes 54
>
> libatomic/
> * configure.ac: Add testsuite/libatomic-site-extra.exp to output
> files.
> * configure: Regenerate.
> * libatomic/testsuite/libatomic-site-extra.exp.in: New file.
> * testsuite/Makefile.am (EXTRA_DEJAGNU_SITE_CONFIG): New
> variable.
> * testsuite/Makefile.in: Regenerate.
OK
jeff
>
next prev parent reply other threads:[~2020-04-06 18:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 23:00 [PATCH v4 0/5] Fix library testsuite " Maciej W. Rozycki
2020-04-03 23:00 ` [PATCH v4 1/5] libatomic/test: Fix " Maciej W. Rozycki
2020-04-06 18:10 ` Jeff Law [this message]
2020-04-06 22:34 ` Maciej W. Rozycki
2023-09-12 11:03 ` libatomic: Consider '--with-build-sysroot=[...]' for target libraries' build-tree testing (instead of build-time 'CC' etc.) [PR109951] (was: [PATCH v4 1/5] libatomic/test: Fix compilation for build sysroot) Thomas Schwinge
2023-10-25 8:32 ` [PING] " Thomas Schwinge
2023-10-26 13:34 ` [PING] libatomic: Consider '--with-build-sysroot=[...]' for target libraries' build-tree testing (instead of build-time 'CC' etc.) [PR109951] Jeff Law
2020-04-03 23:01 ` [PATCH v4 GCC 2/5] libffi/test: Fix compilation for build sysroot Maciej W. Rozycki
2020-04-06 18:06 ` Jeff Law
2020-04-06 20:21 ` Maciej W. Rozycki
2020-04-03 23:01 ` [PATCH v4 GCC 3/5] libffi/test: Make `libffi-init' use $CC_FOR_TARGET Maciej W. Rozycki
2020-04-03 23:01 ` [PATCH v4 4/5] libgo/test: Complement compilation fix for build sysroot Maciej W. Rozycki
2020-04-03 23:01 ` [PATCH v4 5/5] libgomp/test: Remove a build sysroot fix regression Maciej W. Rozycki
2020-04-06 18:11 ` Jeff Law
2020-04-06 22:34 ` Maciej W. Rozycki
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=78cb5a2429cf8b6eb043d86e26a9896214eb6765.camel@redhat.com \
--to=law@redhat.com \
--cc=cltang@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@golang.org \
--cc=macro@wdc.com \
--cc=mikestump@comcast.net \
/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).