-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
failing installation of GCCcore/10.3.0 on top of EESSI 2023.04 compat layer #250
Comments
This problem is fixed if the patched GCC easyblock from easybuilders/easybuild-easyblocks#2921 is used. |
Same problem occurs with Although easybuilders/easybuild-easyblocks#2921 helps with fixing this build problem that happens just a couple of minutes into stage 1 of the GCC bootstrap procedure, it doesn't lead to a fully working installation in that case, since the RPATH part of sanity check for
Indeed, there's no RPATH section in binaries/libraries, although there should be:
In comparison, the successful
Same problem was observed with |
The installation of
So the problem with the failing sanity check seems to only occur when @bartoldeman: Any ideas here? |
@boegel what's the RPATH for GCCcore/10.3.0 on top of EESSI 2023.04 ? |
For NESSI/2023.04 (should be identical to EESSI/2023.04 compat layer), I have
And similar for NESSI/2022.11 which has a compat layer built in November 2022. |
see 2nd |
The installation of No '(RPATH)' found in 'readelf -d' output for /cvmfs/pilot.eessi-hpc.org/versions/2021.12/software/linux/x86_64/amd/zen3/software/GCCcore/11.3.0/lib64/libgcc_s.so.1: |
I compared the logs for building GCC/10.3.0 and for building GCC/11.3.0 (on top of 2023.04), and the only difference I can spot are in options of two configure commands. == Running pre-configure hook... and == building... So difference between 10.3.0 and 11.3.0 is --enable-gold=default --enable-ld --with-plugin-ld=ld.gold and --enable-gold --enable-ld=default. 11.3.0 lacks the --with-plugin-ld=ld.gold. These differences are because of changed settings in the gcc easyblock (lines 532-535)
and gold shall not be used from 11.3.0 because of bitrot (lines 133-135)
|
Updates:
So we need to figure out why the changes in easybuilders/easybuild-easyblocks#2711 are causing trouble when |
I tried GCC 13.1 on our compatibility layer but with |
@bartoldeman Which EasyBuild version were you using there? Does that GCC easyblock that was used include the changes made in easybuilders/easybuild-easyblocks#2711? |
One more clue: some libraries in the
If found That tells me that for some reason |
I looked into a failing build of GCC/11.3.0 on top of NESSI/2023.04. Only a few libraries and binaries have the RPATH section. libraries under
|
I'm currently running the build of |
I installed That revealed the following commands were used for building
This makes sense, since the
Similarly, for the 2nd
For the next
The same goes from the final
Here, the
EasyBuild currently (v4.7.1) doesn't install a wrapper for So, it seems we simply need to make sure there's are also wrapper in place for linker commands prefixed with |
Hook implemented in #251 indeed fixes this problem (along with easybuilders/easybuild-easyblocks#2921 when using EasyBuild v4.7.1), test installation of
|
|
I used EB 4.7.0, so using ld.bfd, but I did still use our ld wrapper with The way our ld wrapper works is as follows:
implemented via: in practice it appears as follows:
Then this wrapper will then determine the binary
|
Overview of
|
only pick a software subdir that is present in the CVMFS repository
The installation of
GCCcore/10.3.0
is failing with EasyBuild v4.7.1 on top of the EESSI pilot 2023.04 compat layer, with:see also NorESSI#96 (cc @trz42)
The text was updated successfully, but these errors were encountered: