Arnd Bergmann dixit:
>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.
Is my expectation that, for any given platform (armel, armhf, arm64),
that a default invocation of the system compiler adds the correct flags
not good?
>However, with arm-linux-gnueabihf-gcc-12, it appears to work fine again.
Sounds like a bug in gcc-11 instead then? (Why has this then not hit
more packages?)
>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?
debian/rules inspects DEB_HOST_ARCH and passes MYARCH to the upstream
Makefile so this ought to DTRT…ish — arm64 is passed as aarch64, and
all other *arm* are passed as arm (though we don’t carry armeb or the
pre-EABI arm any more so that’s probably also fine).
Note that #1017537 (on armel) and #1017538 (on armhf) probably are,
if not the same thing, at least related.
bye,
//mirabilos
--
> Hi, does anyone sell openbsd stickers by themselves and not packaged
> with other products?
No, the only way I've seen them sold is for $40 with a free OpenBSD CD.
-- Haroon Khalid and Steve Shockley in gmane.os.openbsd.misc
