Arch Linux

rmu

Member

Registered: 2015-12-26

Posts: 11

Is arm-none-eabi-gcc broken?

I'm spent days trying to discover the cause of bizarre behavior by two different STM32L4 NUCLEO boards. Last night, I replaced the arm-none-eabi package I built myself with the one installed by "sudo pacman -S arm-none-eabi-gcc".  This morning, I tried the new package out. Here's the result.

[rmu@ThermalCity1 N32Blink1]$ arm-none-eabi-gcc --version
arm-none-eabi-gcc (Arch Repository) 6.2.0
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[rmu@ThermalCity1 N32Blink1]$ arm-none-eabi-gcc -o N32Blink1.o -c -mcpu=cortex-m4 -mthumb -mfloat-abi=hard \
-I/home/rmu/STM32Code/L4/LibraryCode -I/home/rmu/STM32Code/L4/MiscCode N32Blink1.c
as: unrecognized option '-mcpu=cortex-m4'

That last line is a showstopper.