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 Regression] ERROR: couldn't execute "../../../gcc/libgomp/testsuite/flock": no such file or directory
Date: Sat, 02 Mar 2024 00:38:11 +0000	[thread overview]
Message-ID: <bug-113192-4-Xzctnj1xBg@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 #10 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:d4f849c0564fc80938d4d4871810a2b97ace45e7

commit r13-8382-gd4f849c0564fc80938d4d4871810a2b97ace45e7
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Wed Jan 10 13:29:47 2024 +0100

    libgomp: Fix up FLOCK fallback handling [PR113192]

    My earlier change broke Solaris testing, because @FLOCK@ isn't substituted
    just into libgomp/Makefile where it worked, but also the
    testsuite/libgomp-site-extra.exp file where Make variables aren't present
    and can't be substituted.

    The following patch instead computes the absolute srcdir path and uses it
    for FLOCK.

    2024-01-10  Jakub Jelinek  <jakub@redhat.com>

            PR libgomp/113192
            * configure.ac (FLOCK): Use $libgomp_abs_srcdir/testsuite/flock
            instead of \$(abs_top_srcdir)/testsuite/flock.
            * configure: Regenerated.

    (cherry picked from commit 2fb3ee3ee82874e160309344bc3e52afeed8f26a)

  parent reply	other threads:[~2024-03-02  0:38 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 [this message]
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-Xzctnj1xBg@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).