Description of problem: With the update from 2.35.1-7.fc34 to 2.35.1-11.fc34, the octave builds are failing in koschei: libtool: link: g++ -fPIC -DPIC -shared -nostdlib /usr/lib/gcc/x86_64-redhat-linux/10/../../../../lib64/crti.o /usr/lib/gcc/x86_64-redhat-linux/10/crtbeginS.o /usr/lib/gcc/x86_64-redhat-linux/10/crtoffloadbegin.o liboctave/.libs/liboctave_la-liboctave-build-info.o liboctave/.libs/liboctave_la-version.o -Wl,--whole-archive liboctave/array/.libs/libarray.a liboctave/external/blas-xtra/.libs/libxerbla.a liboctave/external/ranlib/.libs/libranlib.a liboctave/external/.libs/libexternal.a liboctave/numeric/.libs/libnumeric.a liboctave/operators/.libs/liboperators.a liboctave/system/.libs/libsystem.a liboctave/util/.libs/libutil.a liboctave/wrappers/.libs/libwrappers.a libgnu/.libs/libgnu.a -Wl,--no-whole-archive -lcurl -lcholmod -lumfpack -lamd -lcamd -lcolamd -lccolamd -lcxsparse -lsuitesparseconfig -larpack -lqrupdate -lfftw3_threads -lfftw3 -lfftw3f_threads -lfftw3f -lflexiblas -lreadline -lncurses -lpcre -ldl -L/usr/lib/gcc/x86_64-redhat-linux/10 -L/usr/lib/gcc/x86_64-redhat-linux/10/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64 -L/usr/lib/gcc/x86_64-redhat-linux/10/../../.. -lgfortran -lquadmath -lutil -lstdc++ -lm -lgomp -lpthread -lc -lgcc_s /usr/lib/gcc/x86_64-redhat-linux/10/crtendS.o /usr/lib/gcc/x86_64-redhat-linux/10/../../../../lib64/crtn.o /usr/lib/gcc/x86_64-redhat-linux/10/crtoffloadend.o -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -pthread -fopenmp -O2 -flto=auto -g -grecord-gcc-switches -fstack-protector-strong -m64 -mtune=generic -flto=auto -Wl,-z -Wl,relro -Wl,--as-needed -Wl,-z -Wl,now -flto -pthread -fopenmp -Wl,-soname -Wl,liboctave.so.7 -o liboctave/.libs/liboctave.so.7.0.1 collect2: fatal error: ld terminated with signal 11 [Segmentation fault], core dumped Version-Release number of selected component (if applicable): 2.35.1-11.fc34 How reproducible: I haven't tried, but the segfault occurred on all 3 koschei arches.
Fixed in binutils-2.35.1-12.fc34 Sorry about this guys. The -11.fc43 update was broken and it has taken me a few days to track down the problem. The problem should now be fixed however, so please try rebuilding octave.
Looks good. Thanks.