An upstream bug in cross-binutils-2.27-3.fc25 causes cross-gcc to fail to build from source. This affects Base Runtime, Rawhide, and F25. The bug is specific to xtensa and is the result of a typo resulting in an incorrect pointer being referenced. The bug eventually causes a build of cross-gcc to fail with a message similar to the following: -------- ... /builddir/build/BUILD/gcc-6.1.1-20160621/xtensa-linux-gnu/./gcc/xgcc -B/builddir/build/BUILD/gcc-6.1.1-20160621/xtensa-linux-gnu/./gcc/ -B/usr/xtensa-linux-gnu/bin/ -B/usr/xtensa-linux-gnu/lib/ -isystem /usr/xtensa-linux-gnu/include -isystem /usr/xtensa-linux-gnu/sys-include -g -O2 -Wall -fexceptions -O2 -g -O2 -Wall -fexceptions -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -fPIC -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -Dinhibit_libc -fPIC -I. -I. -I../.././gcc -I../../../gcc-6.1.1-20160621/libgcc -I../../../gcc-6.1.1-20160621/libgcc/. -I../../../gcc-6.1.1-20160621/libgcc/../gcc -I../../../gcc-6.1.1-20160621/libgcc/../include -DHAVE_CC_TLS -o _cmpsf2_s.o -MT _cmpsf2_s.o -MD -MP -MF _cmpsf2_s.dep -DSHARED -DL_cmpsf2 -xassembler-with-cpp -c ../../../gcc-6.1.1-20160621/libgcc/config/xtensa/lib1funcs.S ../../../gcc-6.1.1-20160621/libgcc/config/xtensa/ieee754-sf.S: Assembler messages: ../../../gcc-6.1.1-20160621/libgcc/config/xtensa/ieee754-sf.S:237: Error: found '', expected: ')' ../../../gcc-6.1.1-20160621/libgcc/config/xtensa/ieee754-sf.S:237: Error: junk at end of line, first unrecognized character valued 0x17 ../../../gcc-6.1.1-20160621/libgcc/config/xtensa/ieee754-sf.S:237: Internal error! Assertion failure in ignore_rest_of_line at ../../binutils-2.27/gas/read.c:3758. Please report this bug. Makefile:457: recipe for target '_addsubsf3_s.o' failed ... -------- Fortunately, there is an upstream patch to fix this bug--and the fixed cross-binutils allows cross-gcc to build from source. See: https://sourceware.org/ml/binutils/2016-09/msg00179.html Upstream commit with fix: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;f=gas/config/tc-xtensa.c;h=78fb7e37eb8bb08ae537d6c487996ff17c810332
Created attachment 1231885 [details] proposed patch to correct FTBFS issue
Please apply the patch or respond with a reason it should not be applied within two weeks. After that time, a provenpackager will go ahead and apply it.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.