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
recommended isl version is 0.16 or 0.15, the minimum required isl version 0.14 is deprecated
checking for isl 0.16 or 0.15... no
*** This configuration is not supported in the following subdirectories:
gnattools gotools target-libada target-libgo target-libffi target-zlib target-libjava target-libobjc target-liboffloadmic target-boehm-gc
(Any other directories should still work fine.)
/tmp/eb-j2xgtx4w/eb-jki7lu51/ccsxayaS.s: Assembler messages:
/tmp/eb-j2xgtx4w/eb-jki7lu51/ccsxayaS.s:11: Error: unknown .loc sub-directive `view'
/tmp/eb-j2xgtx4w/eb-jki7lu51/ccsxayaS.s:11: Error: junk at end of line, first unrecognized character is `-'
/tmp/eb-j2xgtx4w/eb-jki7lu51/ccsxayaS.s:13: Error: unknown .loc sub-directive `view'
/tmp/eb-j2xgtx4w/eb-jki7lu51/ccsxayaS.s:13: Error: unknown pseudo-op: `.lvu1'
/tmp/eb-j2xgtx4w/eb-jki7lu51/ccsxayaS.s:14: Error: unknown .loc sub-directive `view'
/tmp/eb-j2xgtx4w/eb-jki7lu51/ccsxayaS.s:14: Error: unknown pseudo-op: `.lvu2'
*** The command 'gcc -o conftest -g -O2 conftest.c' failed.
*** You must set the environment variable CC to a working compiler.
This turns out to be due to an incompatibility of the assembler from binutils with the system gcc. The solution is therefore to use a newer binutils version as a build dependency, as done in 6224cf5
This probably has little side effects, since the binutils build dependency is only used when bootstrapping. Once GCCcode-6.4.0.eb is installed, you can use that gcc to install a module binutils/2.28-GCCcore-6.4.0 which is used further in the toolchain. When compiling software afterwards, I often see messages like: ld: /vsc-hard-mounts/leuven-apps/rocky8/skylake-6132/2018a/software/GCCcore/6.4.0/bin/../lib/gcc/x86_64-pc-linux-gnu/6.4.0//libgcc.a(_muldi3.o): unable to initialize decompress status for section .debug_info
which might be coming from here. Although annyoing, the seem harmless.
Additionally you hit an error when compiling libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc because <sys/ustat.h> has been removed from recent glibc versions. A patch is provided at https://reviews.llvm.org/rG383fe5c8668f63ef21c646b43f48da9fa41aa100 which is also included in 6224cf5
The text was updated successfully, but these errors were encountered:
Compiling gcc fails with error:
This turns out to be due to an incompatibility of the assembler from binutils with the system gcc. The solution is therefore to use a newer binutils version as a build dependency, as done in 6224cf5
This probably has little side effects, since the binutils build dependency is only used when bootstrapping. Once
GCCcode-6.4.0.eb
is installed, you can use that gcc to install a modulebinutils/2.28-GCCcore-6.4.0
which is used further in the toolchain. When compiling software afterwards, I often see messages like:ld: /vsc-hard-mounts/leuven-apps/rocky8/skylake-6132/2018a/software/GCCcore/6.4.0/bin/../lib/gcc/x86_64-pc-linux-gnu/6.4.0//libgcc.a(_muldi3.o): unable to initialize decompress status for section .debug_info
which might be coming from here. Although annyoing, the seem harmless.
Additionally you hit an error when compiling
libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc
because<sys/ustat.h>
has been removed from recent glibc versions. A patch is provided at https://reviews.llvm.org/rG383fe5c8668f63ef21c646b43f48da9fa41aa100 which is also included in 6224cf5The text was updated successfully, but these errors were encountered: