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 libgomp/113192] [11/12/13/14 Regression] ERROR: couldn't execute "../../../gcc/libgomp/testsuite/flock": no such file or directory Date: Tue, 09 Jan 2024 08:57:09 +0000 [thread overview] Message-ID: <bug-113192-4-fixL9lcVAW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113192-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113192 --- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:f2e967e0257bc8188840df236595e7218b6bf748 commit r14-7027-gf2e967e0257bc8188840df236595e7218b6bf748 Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Jan 9 09:54:06 2024 +0100 libgomp: Use absolute pathname to testsuite/flock [PR113192] When flock program doesn't exist, libgomp configure attempts to offer a fallback version using a perl script, but we weren't using absolute filename to that, so it apparently failed to work correctly. The following patch arranges for it to get the absolute filename. Tested by John David in the PR. 2024-01-09 Jakub Jelinek <jakub@redhat.com> PR libgomp/113192 * configure.ac (FLOCK): Use \$(abs_top_srcdir)/testsuite/flock rather than $srcdir/testsuite/flock. * configure: Regenerated.
next prev parent reply other threads:[~2024-01-09 8:57 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-01 19:30 [Bug libgomp/113192] New: [14 " danglin at gcc dot gnu.org 2024-01-02 15:21 ` [Bug libgomp/113192] [11/12/13/14 " tschwinge at gcc dot gnu.org 2024-01-03 14:23 ` dave.anglin at bell dot net 2024-01-06 6:15 ` pinskia at gcc dot gnu.org 2024-01-06 19:02 ` danglin at gcc dot gnu.org 2024-01-08 20:49 ` jakub at gcc dot gnu.org 2024-01-08 22:43 ` dave.anglin at bell dot net 2024-01-09 8:57 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-09 9:07 ` [Bug libgomp/113192] [11/12/13 " jakub at gcc dot gnu.org 2024-01-10 12:32 ` cvs-commit at gcc dot gnu.org 2024-03-02 0:38 ` cvs-commit at gcc dot gnu.org 2024-03-02 0:38 ` cvs-commit at gcc dot gnu.org 2024-03-04 12:06 ` [Bug libgomp/113192] [11/12 " jakub 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-113192-4-fixL9lcVAW@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).