Starting with gcc-11, Debian's armhf compiler no longer builds with a
default -mfpu= option. Instead it enables the FPU via an extension to
the -march flag (--with-arch=armv7-a+fp). criu's Makefile explicitly
passes its own -march=armv7-a setting, which overrides the +fp
default, so we end up with no FPU:
cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU
I've read the note several times but the behaviour of Configure does
not seem to match it. Rather than actually leaving the options open,
it adds the -march=armv7-a. If it had just picked the base linux-armv4 target, things would have been fine.
tags 1095653 + patchBug #1095653 [src:ruby-build] ruby-build: fails test build-ruby-openssl on unstable/armhf
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (2 / 14) |
Uptime: | 147:37:53 |
Calls: | 10,383 |
Calls today: | 8 |
Files: | 14,054 |
D/L today: |
2 files (1,861K bytes) |
Messages: | 6,417,735 |