Bug#1081201: libc6-dev:amd64 : Breaks: libc6-dev-amd64-cross (< 2.40~) but 2.39-4cross1 is to be installed
Package: libc6-dev-amd64-cross
Followup-For: Bug #1081201
X-Debbugs-Cc: josch@debian.org, doko@debian.org
Hi Josch, Matthias,
I noticed that cross-toolchain-base (72) has landed in unstable today, and I
was quietly hoping that that would resolve what I believe is the same build
problem during Salsa-CI for an ITP package I'm working on.
In particular[1]:
> /usr/lib/ccache/aarch64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/builds/jayaddison/quadrilateralcowboy/debian/output/source_dir=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/cmTC_2ae10.dir/testCCompiler.c.o -c /builds/jayaddison/quadrilateralcowboy/debian/output/source_dir/obj-aarch64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-tJY3pO/testCCompiler.c
> ccache: error: execute_noreturn of /usr/bin/aarch64-linux-gnu-gcc failed: Exec format error
If the answer to this is simply a case of waiting for upload of other toolchain
dependencies, then my apologies for this added distraction. On balance I feel
it's probably better for me to mention (and to provide another sample case)
than to say nothing and assume it'll go away.
FWIW: my limited understanding of crossbuilding is that it should be possible
to build a compiler that runs natively on a host architecture (amd64 for this
runner) yet targets a different architecture (arm64 for this build) -- and so
the "exec format" error is surprising to me (I recognize it instead from
situations where a native binary from a _different_ architecture attempts to
run on a machine; sometimes mitigatable by using qemu-static / binfmt tricks,
but at the kind of performance cost we shouldn't accept during builds).
Regards,
James
[1] - https://salsa.debian.org/jayaddison/quadrilateralcowboy/-/jobs/6397131#L2458
Reply to: