GCC 10.3.0 fails to compile on Manjaro (GCC 12.2, binutils 2.39.0)

[baloe]

I am unable to build GCC 10.3.0. Here is the output:

== Temporary log file in case of crash /tmp/eb-qe86ahz6/easybuild-ubithjku.log
== found valid index for /tmp/bastian/eb_tmp/easybuild/easyconfigs, so using it...
== found valid index for /tmp/bastian/eb_tmp/easybuild/easyconfigs, so using it...
Dry run: printing build status of easyconfigs and dependencies
CFGS=/tmp/bastian/eb_tmp/easybuild/easyconfigs
 * [x] $CFGS/m/M4/M4-1.4.19.eb (module: M4/1.4.19)
 * [x] $CFGS/b/Bison/Bison-3.8.2.eb (module: Bison/3.8.2)
 * [x] $CFGS/f/flex/flex-2.6.4.eb (module: flex/2.6.4)
 * [x] $CFGS/z/zlib/zlib-1.2.11.eb (module: zlib/1.2.11)
 * [x] $CFGS/b/binutils/binutils-2.36.1.eb (module: binutils/2.36.1)
 * [ ] $CFGS/g/GCCcore/GCCcore-10.3.0.eb (module: GCCcore/10.3.0)
 * [ ] $CFGS/z/zlib/zlib-1.2.11-GCCcore-10.3.0.eb (module: zlib/1.2.11-GCCcore-10.3.0)
 * [ ] $CFGS/h/help2man/help2man-1.48.3-GCCcore-10.3.0.eb (module: help2man/1.48.3-GCCcore-10.3.0)
 * [ ] $CFGS/m/M4/M4-1.4.18-GCCcore-10.3.0.eb (module: M4/1.4.18-GCCcore-10.3.0)
 * [ ] $CFGS/b/Bison/Bison-3.7.6-GCCcore-10.3.0.eb (module: Bison/3.7.6-GCCcore-10.3.0)
 * [ ] $CFGS/f/flex/flex-2.6.4-GCCcore-10.3.0.eb (module: flex/2.6.4-GCCcore-10.3.0)
 * [ ] $CFGS/b/binutils/binutils-2.36.1-GCCcore-10.3.0.eb (module: binutils/2.36.1-GCCcore-10.3.0)
 * [ ] $CFGS/g/GCC/GCC-10.3.0.eb (module: GCC/10.3.0)
== Temporary log file(s) /tmp/eb-qe86ahz6/easybuild-ubithjku.log* have been removed.
== Temporary directory /tmp/eb-qe86ahz6 has been removed.
== Temporary log file in case of crash /tmp/eb-u4d40mvn/easybuild-e7ypgify.log
== found valid index for /tmp/bastian/eb_tmp/easybuild/easyconfigs, so using it...
== resolving dependencies ...
== found valid index for /tmp/bastian/eb_tmp/easybuild/easyconfigs, so using it...
== processing EasyBuild easyconfig /tmp/bastian/eb_tmp/easybuild/easyconfigs/g/GCCcore/GCCcore-10.3.0.eb
== building and installing GCCcore/10.3.0...
== fetching files...
== creating build dir, resetting environment...
== starting iteration #0 ...
== ... (took 2 secs)
== unpacking...
== ... (took 10 secs)
== patching...
== preparing...
== configuring...
== FAILED: Installation ended unsuccessfully (build directory: /soft/modules/build/GCCcore/10.3.0/system-system): 
build failed (first 300 chars): cmd " ../configure   --enable-languages=c,c++,fortran --without-cuda-driver 
--enable-offload-targets=nvptx-none --enable-lto --enable-checking=release  --disable-multilib --enable-shared=yes 
--enable-static=yes  --enable-threads=posix  --enable-plugins  --enable-gold=default --enable-ld --with-plugi (took 
15 secs)
== Results of the build can be found in the log file(s) 
/tmp/eb-u4d40mvn/easybuild-GCCcore-10.3.0-20220911.094514.mAgTh.log
0:00:15  0 out of 8 easyconfigs done
ERROR: Build of /tmp/bastian/eb_tmp/easybuild/easyconfigs/g/GCCcore/GCCcore-10.3.0.eb failed (err: 'build failed (first 300 chars): cmd " ../configure   --enable-languages=c,c++,fortran --without-cuda-driver --enable-offload-targets=nvptx-none --enable-lto --enable-checking=release  --disable-multilib --enable-shared=yes --enable-static=yes  --enable-threads=posix  --enable-plugins  --enable-gold=default --enable-ld --with-plugi')

And here is the mentioned log file:
/tmp/eb-u4d40mvn/easybuild-GCCcore-10.3.0-20220911.094514.mAgTh.log

Is this issue possibly related to #16144 ? I think not, because the error message is very different.

The log reads:

configure: error: in `/soft/modules/build/GCCcore/10.3.0/system-system/gcc-10.3.0/stage1_obj':
configure: error: C compiler cannot create executables
See `config.log' for more details

Here is the config.log file:
/soft/modules/build/GCCcore/10.3.0/system-system/gcc-10.3.0/stage1_obj/config.log

This one mentions a bunch of errors, but I have no idea how to fix them:

> grep -nir error /soft/modules/build/GCCcore/10.3.0/system-system/gcc-10.3.0/stage1_obj/config.log
99:gcc: error: unrecognized command-line option '-V'
100:gcc: fatal error: no input files
104:gcc: error: unrecognized command-line option '-qversion'; did you mean '--version'?
105:gcc: fatal error: no input files
120:collect2: error: ld returned 1 exit status
140:configure:4535: error: in `/soft/modules/build/GCCcore/10.3.0/system-system/gcc-10.3.0/stage1_obj':
141:configure:4537: error: C compiler cannot create executables

[baloe]

I guess my system GCC is too new for it to be able to compile the old GCC 10.3.0 module.

Here is the config.log file: /soft/modules/build/GCCcore/10.3.0/system-system/gcc-10.3.0/stage1_obj/config.log

The first error appears in line 99, reading

gcc version 12.1.1 20220730 (GCC) 
configure:4446: $? = 0
configure:4435: gcc -V >&5
gcc: error: unrecognized command-line option '-V'
gcc: fatal error: no input files
compilation terminated.

I just tried a few versions of GCC on an HPC, ranging from 4 to 11. With none of them gcc -V is valid.
I don't get how this could ever have worked.

Is the intended command gcc -v?

Aha, this sheds light on the -V parameter:
https://superuser.com/a/847156

[baloe]

Once the issue regarding the unrecognized command line option -V is fixed, this fix may be needed as well: #16145

[baloe]

related:
#3405

[jfgrimm]

the unrecognized command line option error is not actually an issue, it's just configure determining what compiler is found. It iterates a bunch of options, and some will fail (and this is recorded in the logs).

To me, the following looks like the actual issue :

/soft/modules/software/binutils/2.36.1/bin/ld: /usr/lib/libc.so.6: unknown type [0x13] section `.relr.dyn'
/soft/modules/software/binutils/2.36.1/bin/ld: skipping incompatible /usr/lib/libc.so.6 when searching for /usr/lib/libc.so.6
/soft/modules/software/binutils/2.36.1/bin/ld: cannot find /usr/lib/libc.so.6
/soft/modules/software/binutils/2.36.1/bin/ld: /usr/lib/libc.so.6: unknown type [0x13] section `.relr.dyn'
/soft/modules/software/binutils/2.36.1/bin/ld: skipping incompatible /usr/lib/libc.so.6 when searching for /usr/lib/libc.so.6
/soft/modules/software/binutils/2.36.1/bin/ld: /usr/lib/ld-linux-x86-64.so.2: unknown type [0x13] section `.relr.dyn'
/soft/modules/software/binutils/2.36.1/bin/ld: skipping incompatible /usr/lib/ld-linux-x86-64.so.2 when searching for /usr/lib/ld-linux-x86-64.so.2
/soft/modules/software/binutils/2.36.1/bin/ld: cannot find /usr/lib/ld-linux-x86-64.so.2
/soft/modules/software/binutils/2.36.1/bin/ld: /usr/lib/ld-linux-x86-64.so.2: unknown type [0x13] section `.relr.dyn'
/soft/modules/software/binutils/2.36.1/bin/ld: skipping incompatible /usr/lib/ld-linux-x86-64.so.2 when searching for /usr/lib/ld-linux-x86-64.so.2

What operating system are you building on, and what are your system compiler and binutils versions?

[baloe]

I am on Manjaro, with

• gcc version 12.2.0 (GCC)
• GNU ld (GNU Binutils) 2.39.0

[ocaisa]

Looking at https://bbs.archlinux.org/viewtopic.php?id=278679, I believe the issue here is that the linker the build wants to use (binutils 2.36.1) is too old for your system. The way out of this is probably to just use the system linker (which is newer). You can do this with

eb --filter-deps=binutils GCCcore-10.3.0.eb

to set this for all your installations (probably a wise move) you can use the easybuild config file or

export EASYBUILD_FILTER_DEPS=binutils

[baloe]

The way out of this is probably to just use the system linker (which is newer). You can do this with

eb --filter-deps=binutils GCCcore-10.3.0.eb

Unfortunately, I was still not successful on my system:

== Temporary log file in case of crash /tmp/eb-wdd3b94y/easybuild-oe4qol7c.log
== found valid index for /tmp/bastian/eb_tmp/easybuild/easyconfigs, so using it...
== found valid index for /tmp/bastian/eb_tmp/easybuild/easyconfigs, so using it...
Dry run: printing build status of easyconfigs and dependencies
CFGS=/tmp/bastian/eb_tmp/easybuild/easyconfigs
 * [x] $CFGS/m/M4/M4-1.4.19.eb (module: M4/1.4.19)
 * [ ] $CFGS/g/GCCcore/GCCcore-10.3.0.eb (module: GCCcore/10.3.0)
 * [ ] $CFGS/g/GCC/GCC-10.3.0.eb (module: GCC/10.3.0)
== Temporary log file(s) /tmp/eb-wdd3b94y/easybuild-oe4qol7c.log* have been removed.
== Temporary directory /tmp/eb-wdd3b94y has been removed.
== Temporary log file in case of crash /tmp/eb-n9qdjdfy/easybuild-rqgo0e52.log
== found valid index for /tmp/bastian/eb_tmp/easybuild/easyconfigs, so using it...
== resolving dependencies ...
== found valid index for /tmp/bastian/eb_tmp/easybuild/easyconfigs, so using it...
== processing EasyBuild easyconfig /tmp/bastian/eb_tmp/easybuild/easyconfigs/g/GCCcore/GCCcore-10.3.0.eb
== building and installing GCCcore/10.3.0...
== fetching files...
== ... (took 3 secs)
== creating build dir, resetting environment...
== starting iteration #0 ...
== ... (took 4 secs)
== unpacking...
== ... (took 10 secs)
== patching...
== preparing...
== configuring...
== ... (took 3 secs)
== building...
== ... (took 21 mins 53 secs)
== FAILED: Installation ended unsuccessfully (build directory: /soft/modules/build/GCCcore/10.3.0/system-system): build failed (first 300 chars): cmd " make -j 4 " exited with exit code 2 and output:
make[1]: Entering directory '/soft/modules/build/GCCcore/10.3.0/system-system/gcc-10.3.0/stage1_obj'
mkdir -p -- ./intl
mkdir -p -- ./libiberty
mkdir -p -- ./fixincludes
mkdir -p -- ./gmp
Configuring in ./intl
Configuring in ./libiberty
Configuri (took 22 mins 14 secs)
== Results of the build can be found in the log file(s) /tmp/eb-n9qdjdfy/easybuild-GCCcore-10.3.0-20221027.224031.hjDGl.log
0:22:14  0 out of 2 easyconfigs done
ERROR: Build of /tmp/bastian/eb_tmp/easybuild/easyconfigs/g/GCCcore/GCCcore-10.3.0.eb failed (err: 'build failed (first 300 chars): cmd " make -j 4 " exited with exit code 2 and output:\nmake[1]: Entering directory \'/soft/modules/build/GCCcore/10.3.0/system-system/gcc-10.3.0/stage1_obj\'\nmkdir -p -- ./intl\nmkdir -p -- ./libiberty\nmkdir -p -- ./fixincludes\nmkdir -p -- ./gmp\nConfiguring in ./intl\nConfiguring in ./libiberty\nConfiguri')

/tmp/eb-n9qdjdfy/easybuild-GCCcore-10.3.0-20221027.224031.hjDGl.log

[baloe]

The remaining error is probably

In file included from /usr/include/linux/fs.h:19,
                 from ../../../../libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:75:
/usr/include/linux/mount.h:95:6: error: multiple definition of enum fsconfig_command
   95 | enum fsconfig_command {
      |      ^~~~~~~~~~~~~~~~
In file included from ../../../../libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:62:
/soft/modules/build/GCCcore/10.3.0/system-system/gcc-10.3.0/stage1_obj/gcc/include-fixed/sys/mount.h:249:6: note: previous definition here
  249 | enum fsconfig_command
      |      ^~~~~~~~~~~~~~~~
In file included from /usr/include/linux/fs.h:19,
                 from ../../../../libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:75:
/usr/include/linux/mount.h:129:8: error: redefinition of struct mount_attr
  129 | struct mount_attr {
      |        ^~~~~~~~~~
In file included from ../../../../libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:62:
/soft/modules/build/GCCcore/10.3.0/system-system/gcc-10.3.0/stage1_obj/gcc/include-fixed/sys/mount.h:219:8: note: previous definition of struct mount_attr
  219 | struct mount_attr
      |        ^~~~~~~~~~
make[4]: *** [Makefile:611: sanitizer_platform_limits_posix.lo] Error 1

I had run into the exact same issue when trying to install GCC 11, and @branfosj and @boegel were able to fix it: #16144 (comment)