Qmk_firmware: ld link Error: Conflicting CPU architectures 13/1

[kb3dow]

Compiling for the Infinity60 keyboard gives a linking error saying
Conflicting CPU architectures.
% make infinity60:default
gives at the end ...
Assembling: lib/chibios/os/common/ports/ARMCMx/compilers/GCC/chcoreasm_v7m.S [OK]
Linking: .build/infinity60_default.elf [ERRORS]
|
| /usr/lib/gcc/arm-none-eabi/6.3.1/../../../arm-none-eabi/bin/ld: error: /usr/lib/gcc/arm-none-eabi/6.3.1/../../../arm-none-eabi/lib/crt0.o: Conflicting CPU architectures 13/1
| /usr/lib/gcc/arm-none-eabi/6.3.1/../../../arm-none-eabi/bin/ld: failed to merge target specific data of file /usr/lib/gcc/arm-none-eabi/6.3.1/../../../arm-none-eabi/lib/crt0.o
| collect2: error: ld returned 1 exit status
|
tmk_core/rules.mk:290: recipe for target '.build/infinity60_default.elf' failed
make[1]: * [.build/infinity60_default.elf] Error 1
Make finished with errors
Makefile:535: recipe for target 'infinity60:default' failed
make: * [infinity60:default] Error 1

[sebirdman]

I had the same issue:

Sounds like this is a bug with ubuntu: https://github.com/bbcmicrobit/micropython/issues/514#issuecomment-404759614

The fix there seems to have fixed it here as well.

[kb3dow]

Great, thanks.
I tried it out and your suggestion (as mentioned in that link) works!

On Mon, Mar 11, 2019, 10:47 PM Stephen Bird [e-mail]
wrote:

I had the same issue:

Sounds like this is a bug with ubuntu: bbcmicrobit/micropython#514
(comment)
https://github.com/bbcmicrobit/micropython/issues/514#issuecomment-404759614

The fix there seems to have fixed it here as well.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/qmk/qmk_firmware/issues/5369#issuecomment-471830613,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AG8KhwKtM0D3diM02xIc71060A6Evy6Xks5vVxVMgaJpZM4bpcPB
.

[kb3dow]

I had the same issue:

Sounds like this is a bug with ubuntu: bbcmicrobit/micropython#514 (comment)

The fix there seems to have fixed it here as well.

That fixes the issue.