Bug 1747833 - After upgrade, cross-compiler no longer links
Summary: After upgrade, cross-compiler no longer links
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: arm-none-eabi-newlib
Version: 30
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Michal Hlavinka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-02 02:23 UTC by Mark Fassler
Modified: 2019-09-11 03:12 UTC (History)
3 users (show)

Fixed In Version: arm-none-eabi-newlib-3.1.0-3.fc30
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-11 03:12:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Mark Fassler 2019-09-02 02:23:25 UTC
Description of problem:
After running a "dnf update", compiler no longer links my binary.


Version-Release number of selected component (if applicable):

Working:      arm-none-eabi-gcc-cs-1:7.4.0-1.fc30.x86_64
Not working:  arm-none-eabi-gcc-cs-1:9.2.0-1.fc30.x86_64

(I also have the same problem on fc29)



How reproducible:

100%.  After "dnf upgrade", if I do a clean build from scratch, the linker fails.  If I downgrade to 7.4.0, if I do a clean build from scratch, everything works.


Steps to Reproduce:
1.  git clone https://github.com/mfassler/atdrive-moab.git
2.  follow the prep steps in "howto-build-mbed-os-on-linux.txt"
3.  ln -s ROBOT_CONFIG_followbot1.hpp ROBOT_CONFIG.hpp
3.  make


Actual results:

At the final, linking step (using version 9.2.0):

link: atdrive-moab.elf
/usr/lib/gcc/arm-none-eabi/9.2.0/../../../../arm-none-eabi/bin/ld: error: /usr/lib/gcc/arm-none-eabi/9.2.0/../../../../arm-none-eabi/lib/crt0.o: conflicting CPU architectures 13/0
/usr/lib/gcc/arm-none-eabi/9.2.0/../../../../arm-none-eabi/bin/ld: failed to merge target specific data of file /usr/lib/gcc/arm-none-eabi/9.2.0/../../../../arm-none-eabi/lib/crt0.o
/usr/lib/gcc/arm-none-eabi/9.2.0/../../../../arm-none-eabi/bin/ld: error: /usr/lib/gcc/arm-none-eabi/9.2.0/../../../../arm-none-eabi/lib/libc.a(lib_a-setjmp.o): conflicting CPU architectures 13/0
/usr/lib/gcc/arm-none-eabi/9.2.0/../../../../arm-none-eabi/bin/ld: failed to merge target specific data of file /usr/lib/gcc/arm-none-eabi/9.2.0/../../../../arm-none-eabi/lib/libc.a(lib_a-setjmp.o)
collect2: error: ld returned 1 exit status
make[1]: *** [/pubfiles/github/mfassler/atdrive-moab/Makefile:1808: atdrive-moab.elf] Error 1
make: *** [Makefile:26: all] Error 2



Expected results:

At the final, linking step (using version 7.4.0):

link: atdrive-moab.elf
arm-none-eabi-objcopy -O binary atdrive-moab.elf atdrive-moab.bin
===== bin file ready to flash: BUILD/atdrive-moab.bin =====
arm-none-eabi-objcopy -O ihex atdrive-moab.elf atdrive-moab.hex

Comment 1 Fedora Update System 2019-09-02 14:40:40 UTC
FEDORA-2019-a50106f40d has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-a50106f40d

Comment 2 Fedora Update System 2019-09-03 02:56:56 UTC
arm-none-eabi-newlib-3.1.0-3.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-a50106f40d

Comment 3 Mark Fassler 2019-09-03 06:32:05 UTC
The new rpm solves my problem on fc29 and fc30.  Thank you.

Comment 4 Fedora Update System 2019-09-11 03:12:54 UTC
arm-none-eabi-newlib-3.1.0-3.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.