OK, so I am on CentOS 7 and so have installed glibc-devel-i686
but now I get the error: gcc -o OpenBUGSCli OpenBUGSCli.c -L ../lib -Wl,-rpath,\$ORIGIN/../lib -m32 -lOpenBUGS /trinity/shared/easybuild/software/binutils/2.34-GCCcore-9.3.0/bin/ld.gold: error: /trinity/shared/easybuild/software/GCCcore/9.3.0/lib/gcc/x86_64-pc-linux-gnu/9.3.0/crtbegin.o: incompatible target /trinity/shared/easybuild/software/binutils/2.34-GCCcore-9.3.0/bin/ld.gold: error: /trinity/shared/easybuild/software/GCCcore/9.3.0/lib/gcc/x86_64-pc-linux-gnu/9.3.0/crtend.o: incompatible target /trinity/shared/easybuild/software/binutils/2.34-GCCcore-9.3.0/bin/ld.gold: error: cannot find -lgcc_s /trinity/shared/easybuild/software/binutils/2.34-GCCcore-9.3.0/bin/ld.gold: error: cannot find -lgcc_s So I seem to be trying to link 32 and 64 bit objects. Aren't I going to need a 32-bit versions of crtbegin.o etc.? Åke Sandgren <ake.sandg...@hpc2n.umu.se> writes: > That one comes from libc6-dev-i386 or similar for RH based systems. > > On 12/1/20 2:28 PM, Loris Bennett wrote: >> Hi, >> >> I am getting the following error with the foss-2020a toolchain: >> >> /usr/include/gnu/stubs.h:7:11: fatal error: gnu/stubs-32.h: No such file >> or directory >> 7 | # include <gnu/stubs-32.h> >> >> Am I right in assuming that the toolchain would have to be compiled >> with >> >> m32=True >> >> to avoid this problem? >> >> Cheers, >> >> Loris >> -- Dr. Loris Bennett (Hr./Mr.) ZEDAT, Freie Universität Berlin Email loris.benn...@fu-berlin.de
