Your message dated Wed, 29 Nov 2023 17:27:41 +0100
with message-id <ZWdmfS_zAI-7Bk1d@ariel>
and subject line Re: Bug#1050216: cpu-features: FTBFS on armhf, armel
"Including cpuinfo_aarch64.h from a non-aarch64 target"
has caused the Debian Bug report #1050216,
regarding cpu-features: FTBFS on armhf, armel "Including cpuinfo_aarch64.h from
a non-aarch64 target"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1050216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050216
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: cpu-features
Version: 0.7.0-1
Severity: serious
Tags: sid trixie ftbfs
User: [email protected]
Usertags: armhf armel
Hi,
cpu-features fails to build on armhf and armel with the following error:
In file included from /<<PKGBUILDDIR>>/test/cpuinfo_aarch64_test.cc:15:
/<<PKGBUILDDIR>>/test/../include/cpuinfo_aarch64.h:155:2: error: #error
"Including cpuinfo_aarch64.h from a non-aarch64 target."
155 | #error "Including cpuinfo_aarch64.h from a non-aarch64 target."
| ^~~~~
make[3]: *** [test/CMakeFiles/cpuinfo_aarch64_test.dir/build.make:79:
test/CMakeFiles/cpuinfo_aarch64_test.dir/cpuinfo_aarch64_test.cc.o] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-arm-linux-gnueabi'
make[2]: *** [CMakeFiles/Makefile2:1400:
test/CMakeFiles/cpuinfo_aarch64_test.dir/all] Error 2
--- End Message ---
--- Begin Message ---
Hi!
On 2023-11-08 03:59, Shengjing Zhu wrote:
> or maybe you have a different setup then buildd?
Indeed that was it. I checked the buildds config, and for armhf/armel
they have personality=linux32 in the schroot settings, which I did not
have in mine. [1] Setting personality=linux32, cpu-features builds fine
in a armhf chroot on my arm64 host.
In terms of why the build was failing: CMakeLists.txt checks if
CMAKE_SYSTEM_PROCESSOR looks like aarch64 [2], and if it does then
cpuinfo_aarch64.h is included [3]. Finally, cpuinfo_aarch64.h errors out
if actual aarch64 features are not supported [4].
There may be problems in general when cross-building cpu-features under
certain configurations I suspect, see for example [5]. That being said,
that's an entirely different sort of bug so I'm closing this now.
Thanks,
Emanuele
[1]
https://salsa.debian.org/dsa-team/mirror/dsa-puppet/-/blob/production/modules/schroot/files/setup-dchroot#L138
[2] https://sources.debian.org/src/cpu-features/0.9.0-1/CMakeLists.txt/#L82
[3] https://sources.debian.org/src/cpu-features/0.9.0-1/CMakeLists.txt/#L108
[4]
https://sources.debian.org/src/cpu-features/0.9.0-1/include/cpuinfo_aarch64.h/#L298
[5] https://github.com/gnuradio/volk/issues/445
--- End Message ---
