public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/113192] [11/12 Regression] ERROR: couldn't execute "../../../gcc/libgomp/testsuite/flock": no such file or directory
Date: Mon, 04 Mar 2024 12:06:41 +0000 [thread overview]
Message-ID: <bug-113192-4-iWJAaywr1e@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
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[11/12/13 Regression] |[11/12 Regression] ERROR:
|ERROR: couldn't execute |couldn't execute
|"../../../gcc/libgomp/tests |"../../../gcc/libgomp/tests
|uite/flock": no such file |uite/flock": no such file
|or directory |or directory
--- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Should be now fixed for GCC 13 too.
prev parent reply other threads:[~2024-03-04 12:06 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
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 ` jakub 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-113192-4-iWJAaywr1e@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).