FTBFS against gcc 11 on armhf
Bug #1941920 reported by
Dan Bungert
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rust-curl-sys (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
rust-openssl-sys (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
While tracing the build failure of rust-curl-sys on armhf, I observed that both rust-curl-sys and rust-openssl-sys will FTBFS with gcc-11. gcc-10 seems fine.
I was able to verify this locally in an impish armhf container running on raspberry pi 4, and also in PPA builds.
gcc 10: https:/
gcc 11: https:/
description: | updated |
To post a comment you must log in.
[openssl-sys 0.9.55] running: "cc" "-O0" "-ffunction- sections" "-fdata-sections" frame-pointer" "-march=armv7-a" "-g" "-O2" "-ffile-pref /usr/share/ cargo/registry/ openssl- sys-0.9. 55=." "-fstack- protector- strong format- security" "-I" "/usr/include" "-E" "build/expando.c
"-fPIC" "-g" "-fno-omit-
ix-map=
" "-Wformat" "-Werror=
"
[openssl-sys 0.9.55] cargo:warning=cc1: error: ‘-mfloat-abi=hard’: selected architecture lacks an FPU
This is actually a bug in gcc-11, which had the wrong target. It is fixed by the gcc-11 in -proposed.