From: "Maciej W. Rozycki" <macro@wdc.com>
To: gcc-patches@gcc.gnu.org
Cc: libffi-discuss@sourceware.org, golang-dev@googlegroups.com
Subject: [PATCH 0/4] Fix library testsuite compilation for build sysroot
Date: Mon, 11 Nov 2019 18:12:00 -0000 [thread overview]
Message-ID: <alpine.LFD.2.21.1911081714120.13542@redsun52.ssa.fujisawa.hgst.com> (raw)
Hi,
This patch series addresses a problem with the testsuite compiler being
set up across libatomic, libffi, libgo, libgomp with no correlation
whatsoever to the target compiler being used in GCC compilation.
Consequently there in no arrangement made to set up the compilation
sysroot according to the build sysroot specified for GCC compilation,
causing a catastrophic failure across the testsuites affected from the
inability to link executables.
The fix is based on a similar arrangement already made for passing
autoconf output variables in libgomp, and uses the GCC_UNDER_TEST (or
GOC_UNDER_TEST, as applicable) TCL variable already used across several
GCC library testsuites.
Verified with a cross-compiler configured for the `riscv-linux-gnu'
target and the `x86_64-linux-gnu' host and using RISC-V/Linux QEMU in the
user emulation mode as the target board. Also no change in results with
`x86_64-linux-gnu' native regression testing.
See individual change descriptions for details.
OK to apply to the GCC repo (for libraries maintained externally I'll be
happy to assist with any merging required, although given that these
changes are confined to autoconf/automake scriptery they should be
straightforward to apply, barring any conflicts in generated files)?
Maciej
next reply other threads:[~2019-11-11 18:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 18:12 Maciej W. Rozycki [this message]
2019-11-11 18:12 ` [PATCH 1/4] libatomic/test: Fix " Maciej W. Rozycki
2019-11-11 18:12 ` [PATCH 2/4] libffi/test: " Maciej W. Rozycki
2019-11-11 18:15 ` [golang-dev] [PATCH 0/4] Fix library testsuite " Ulderico Cirello
2019-11-11 18:23 ` Kaz Kylheku (libffi)
2019-11-11 18:35 ` Ian Lance Taylor
2019-11-11 18:50 ` Kaz Kylheku (libffi)
2019-11-11 18:33 ` Ian Lance Taylor
2019-11-11 18:44 ` Maciej W. Rozycki
2019-11-11 23:16 ` Ian Lance Taylor
2019-11-11 18:42 ` 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=alpine.LFD.2.21.1911081714120.13542@redsun52.ssa.fujisawa.hgst.com \
--to=macro@wdc.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=golang-dev@googlegroups.com \
--cc=libffi-discuss@sourceware.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).