On Wed, Aug 17, 2022 at 8:00 PM Thorsten Glaser <t...@mirbsd.de> wrote:
>
> Arnd Bergmann dixit:
>
> >-march=armv7-a+fp instead of -march=armv7-a to pick the right
>
> “instead of”
>
> We pass nothing there, and we need a solution (or two distinct
> ones) for armel and armhf.
I tried cross-building it myself now and found the same issue with
an older arm-linux-gnueabihf-gcc-11, which invokes the assembler as
/usr/lib/gcc-cross/arm-linux-gnueabihf/11/../../../../arm-linux-gnueabihf/bin/as
-v -march=armv7-a -mfloat-abi=hard -meabi=5 -o bin-arm/__longjmp.o
longjmp.s
where the old one would pass an extra -mfpu=vfpv3-d16.
However, with arm-linux-gnueabihf-gcc-12, it appears to work fine again.
I also see that the Makefile attempts to detect the host architecture, but
fails to recognize armv8 hardware as arm. What hardware and toolchain
environment was the failing build on?
Arnd
