I don't know too much about the testsuite infrastructure. You'll likely need to ping jakub or tobias, who seem to be the most active gomp contributors.
On my FreeBSD system, I have my sources in gcc/gccx, build in gcc/objx, and install into $HOME/work/x. For building and testing, I have a script that ends with # MAKE is required to get the right make(1) propagated through # the 'make' process including the check-fortran phase. # MAKE=gmake export MAKE ../gccx/configure --prefix=$HOME/work/x --enable-languages=c,c++,fortran,lto \ --enable-bootstrap --disable-nls --disable-multilib --disable-libssp \ --enable-initfini-array sleep 1 nice gmake -j6 bootstrap sleep 1 cd gcc nice gmake -j6 check-fortran sleep 1 tail testsuite/gfortran/gfortran.sum Most of the tests that fail have the following log file entry ==3733==ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PRELOAD. FAIL: gfortran.dg/asan/pointer_assign_16.f90 -fsanitize=address -O0 execution test I've never been able to track down how to fix this. It would seem to me that if some ASan lib needs to come first, then it should proactively preload the requisite libraries during testing. -- steve On Fri, Jun 07, 2024 at 09:39:14AM +0200, Andre Vehreschild wrote: > Hi Steve, > > there have not been any answers yet, so thank you for looking into that. I > tried your proposal and changed the installation directory to: > > /mnt/work_store/gcc/installs/dev > > Unfortunately this did not change anything. The gomp-tests are still unable to > compile. But I don't see any issues with libsanitizer tests (at least nothing > is reported) nor any issues with gmake, make and $MAKE. Looks like that is > some > Fedora 39 oddity perhaps? Do you have any pointers who might have insight in > this expect stuff and could shed a light why this GFORTRAN_UNDER_TEST is > checked in the gomp tests only when the libs are not found? > > > PS: Welcome back to the gfortran effort. > > Thanks, I hope to produce a constant stream of patches in the next year or > even > longer. > > Thank you for your time. If you have any other idea that I could test, please > let me know. > > Regards, > Andre > -- > Andre Vehreschild * Email: vehre ad gmx dot de -- Steve
