public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/109951] [14 Regression] libgomp, testsuite: non-native multilib c++ tests fail on Darwin.
Date: Thu, 26 Oct 2023 16:05:24 +0000 [thread overview]
Message-ID: <bug-109951-4-uOWbnP2aJn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109951-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109951
--- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Thomas Schwinge <tschwinge@gcc.gnu.org>:
https://gcc.gnu.org/g:d8ff4b96b4be3bb4346c045bd0a7337079eabf90
commit r14-4949-gd8ff4b96b4be3bb4346c045bd0a7337079eabf90
Author: Thomas Schwinge <thomas@codesourcery.com>
Date: Mon Sep 11 11:36:31 2023 +0200
libatomic: Consider '--with-build-sysroot=[...]' for target libraries'
build-tree testing (instead of build-time 'CC' etc.) [PR109951]
Similar to commit fb5d27be272b71fb9026224535fc73f125ce3be7
"libgomp: Consider '--with-build-sysroot=[...]' for target libraries'
build-tree testing (instead of build-time 'CC' etc.) [PR91884, PR109951]",
this is commit 5ff06d762a88077aff0fb637c931c64e6f47f93d
"libatomic/test: Fix compilation for build sysroot" done differently,
avoiding build-tree testing use of any random gunk that may appear in
build-time 'CC'.
PR testsuite/109951
libatomic/
* configure.ac: 'AC_SUBST(SYSROOT_CFLAGS_FOR_TARGET)'.
* Makefile.in: Regenerate.
* configure: Likewise.
* testsuite/Makefile.in: Likewise.
* testsuite/lib/libatomic.exp (libatomic_init): If
'--with-build-sysroot=[...]' was specified, use it for build-tree
testing.
* testsuite/libatomic-site-extra.exp.in (GCC_UNDER_TEST): Don't
set.
(SYSROOT_CFLAGS_FOR_TARGET): Set.
prev parent reply other threads:[~2023-10-26 16:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 7:23 [Bug testsuite/109951] New: " iains at gcc dot gnu.org
2023-05-24 7:25 ` [Bug testsuite/109951] " iains at gcc dot gnu.org
2023-05-24 10:39 ` iains at gcc dot gnu.org
2023-05-25 7:38 ` rguenth at gcc dot gnu.org
2023-05-25 22:04 ` tschwinge at gcc dot gnu.org
2023-05-25 23:12 ` iains at gcc dot gnu.org
2023-05-25 23:34 ` iains at gcc dot gnu.org
2023-06-01 16:02 ` tschwinge at gcc dot gnu.org
2023-06-02 10:00 ` tschwinge at gcc dot gnu.org
2023-06-02 10:08 ` tschwinge at gcc dot gnu.org
2023-06-02 14:31 ` iains at gcc dot gnu.org
2023-09-12 9:32 ` cvs-commit at gcc dot gnu.org
2023-09-12 9:32 ` cvs-commit at gcc dot gnu.org
2023-09-12 11:32 ` tschwinge at gcc dot gnu.org
2023-09-12 20:20 ` cvs-commit at gcc dot gnu.org
2023-10-26 16:05 ` cvs-commit at gcc dot gnu.org
2023-10-26 16:05 ` cvs-commit at gcc dot gnu.org [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=bug-109951-4-uOWbnP2aJn@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).