public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112862] [14 regression] gfortran.dg coarray tests FAIL on macOS 12+ Date: Thu, 18 Jan 2024 10:14:28 +0000 [thread overview] Message-ID: <bug-112862-4-KEZN2rKHF7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112862-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112862 --- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #3 from Iain Sandoe <iains at gcc dot gnu.org> --- > OK. So I realise the reason you see this and I wasn't: I have the habit of > installing before running the testsuite. When I test uninstalled, then I get > the issue. Right: I always avoid installing before testing to make extra certain to test the freshly built bits and nothing else. > Now I have a concern that we have instances of -Bpath/to/libsomething/.libs > that are present to allow for specs substitution and we also need them for > providing run paths at test time. BUT, we do not want duplicates (since, that > triggers a different warning for some Xcode versions, and is inefficient anyway > - albeit probably a very minor contribution to testing time). Still there is going to be an impact, even on non-Darwin. However, this duplication of -B and -L options is present all over the testsuite already, just nobody cared to do something about it so far. Those Xcode 15 ld warnings my change this, though... > So I think that gcc/lib/gfortran.exp needs to have the library -B/-L additions > structured so that only one set gets added. I'll draft a patch for you to try. Great, thanks.
next prev parent reply other threads:[~2024-01-18 10:14 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-05 11:40 [Bug target/112862] New: " ro at gcc dot gnu.org 2023-12-05 11:40 ` [Bug target/112862] " ro at gcc dot gnu.org 2024-01-16 17:03 ` iains at gcc dot gnu.org 2024-01-17 10:14 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-01-17 21:07 ` iains at gcc dot gnu.org 2024-01-17 21:07 ` iains at gcc dot gnu.org 2024-01-18 10:14 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message] 2024-01-18 18:19 ` iains at gcc dot gnu.org 2024-01-19 14:48 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-01-24 8:15 ` iains at gcc dot gnu.org 2024-01-24 14:45 ` ro at gcc dot gnu.org 2024-01-24 14:48 ` iains at gcc dot gnu.org 2024-01-24 15:01 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-01-24 15:33 ` iains at gcc dot gnu.org 2024-01-28 15:14 ` iains at gcc dot gnu.org 2024-02-02 9:01 ` cvs-commit at gcc dot gnu.org 2024-02-02 9:04 ` iains at gcc dot gnu.org 2024-02-10 15:22 ` [Bug target/112862] " iains at gcc dot gnu.org 2024-05-07 7:42 ` rguenth at gcc dot gnu.org
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-112862-4-KEZN2rKHF7@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: linkBe 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).