You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After fixing binutils on OpenSUSE Leap 15.2 I'm trying to build the full foss/2020a toolchain.
During the build of GCCcore/9.3.0 while configuring ISL for stage 2 with the following run_cmd command, it finds the header but not the static library in the stage2 prefix:
checking which gmp to use... system
checking gmp.h usability... yes
checking gmp.h presence... yes
checking for gmp.h... yes
checking for main in -lgmp... no
configure: error: gmp library not found
The failing config.log test uses this command line:
The given -L/tmp/eb-build/GCCcore/9.3.0/system-system/gcc-9.3.0/stage2_stuff/lib location for GMP is incorrect as on this platform, the library is in a lib64 directory: /tmp/eb-build/GCCcore/9.3.0/system-system/gcc-9.3.0/stage2_stuff/lib64/libgmp.a
@bartoldeman found a part in gcc.py that assumes that libraries are installed in a lib directory, not sure if that's a root cause or just an attempt to plaster over this GCC build behaviour on some platforms:
@zao So this would need a small change in the GCC easyblock to also consider lib64 if that lib dir was not found, rather than blindly assuming it's there?
boegel
added a commit
to boegel/easybuild-easyblocks
that referenced
this issue
Feb 18, 2021
After fixing binutils on OpenSUSE Leap 15.2 I'm trying to build the full foss/2020a toolchain.
During the build of GCCcore/9.3.0 while configuring ISL for stage 2 with the following
run_cmd
command, it finds the header but not the static library in the stage2 prefix:The failing
config.log
test uses this command line:The given
-L/tmp/eb-build/GCCcore/9.3.0/system-system/gcc-9.3.0/stage2_stuff/lib
location for GMP is incorrect as on this platform, the library is in alib64
directory:/tmp/eb-build/GCCcore/9.3.0/system-system/gcc-9.3.0/stage2_stuff/lib64/libgmp.a
@bartoldeman found a part in
gcc.py
that assumes that libraries are installed in alib
directory, not sure if that's a root cause or just an attempt to plaster over this GCC build behaviour on some platforms:easybuild-easyblocks/easybuild/easyblocks/g/gcc.py
Lines 595 to 601 in 6e63e14
The text was updated successfully, but these errors were encountered: