https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113192
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[14 Regression] ERROR: |[11/12/13/14 Regression] |couldn't execute |ERROR: couldn't execute |"../../../gcc/libgomp/tests |"../../../gcc/libgomp/tests |uite/flock": no such file |uite/flock": no such file |or directory |or directory Blocks| |66005 Version|14.0 |11.0 --- Comment #1 from Thomas Schwinge <tschwinge at gcc dot gnu.org> --- (In reply to John David Anglin from comment #0) > HP-UX doesn't have flock but it does have perl. configure tries to create > a fallback but a relative path to libgomp/testsuite/flock is generated. > It is wrong when the testsuite is run. > > AC_MSG_NOTICE([checking for flock implementation]) > AC_CHECK_PROGS(FLOCK, flock) > # Fallback if 'perl' is available. > if test -z "$FLOCK"; then > AC_CHECK_PROG(FLOCK, perl, $srcdir/testsuite/flock) > fi Aha, sorry. Does it work if you changes: -AC_CHECK_PROG(FLOCK, perl, $srcdir/testsuite/flock) +AC_CHECK_PROG(FLOCK, perl, $ac_abs_srcdir/testsuite/flock) ..., so that this: > configure: checking for flock implementation > checking for flock... no > checking for perl... ../../../gcc/libgomp/testsuite/flock ... turns into an absolute path, to resolve: > Running /home/dave/gnu/gcc/gcc/libgomp/testsuite/libgomp.c/c.exp ... > ERROR: tcl error sourcing > /home/dave/gnu/gcc/gcc/libgomp/testsuite/libgomp.c/c.exp. > ERROR: tcl error code NONE > ERROR: couldn't execute "../../../gcc/libgomp/testsuite/flock": no such file > or directory ... this. If that works, and you submit a patch, please in the commit log cite this commit: > This problem was introduced by the following commit: > > commit 04abe1944d30eb18a2060cfcd9695d085f7b4752 > Author: Thomas Schwinge <tho...@codesourcery.com> > Date: Mon May 15 20:00:07 2023 +0200 > > Support parallel testing in libgomp: fallback Perl 'flock' [PR66005] ..., and also specify 'PR testsuite/66005' in the commit log. If that suggestion doesn't easily resolve this issue, then I'll be able to look into it next week. > It appears this problem can be worked around by exporting FLOCK. But only if that specifies an absolute path (or a "suitable" relative one), I suppose? I've also set this "11/12/13 Regression", as these branches use the exact same code. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66005 [Bug 66005] libgomp make check time is excessive