So to make sure I understand - cross-compiling Debian->Pi arm64 is fine,
but even generic C binaries aren't guaranteed to work on Pi armhf,
and the best way to compile a Pi armhf binary on Debian is with qemubuilder?
Given how much time this has/will cost me, I'm minded to propose a
section in https://wiki.debian.org/CrossCompiling so the next person
doesn't have the same problem. Anywhere else I could add this?
On 04/04/2025 17:19, Marcin Juszkiewicz wrote:
W dniu 4.04.2025 o 18:08, Andrew Sayers pisze:
Package: libstdc++-12-dev
Version: 12.2.0-14+rpi1
Severity: important
X-Debbugs-Cc: debian-...@lists.debian.org
User: debian-...@lists.debian.org
Usertags: armhf
The _GLIBCXX_HAVE_ATOMIC_LOCK_POLICY setting differs between Debian
and Raspberry Pi OS, causing programs cross-compiled for Debian
Bookworm armhf
to appear to run on Rasbperry Pi OS Bookworm armhf, then later crash
for no obvious reason.
Debian, like many other distributions, agreed years ago that armhf is
ARMv7 with vfp3d16.
Raspberry/Pi OS reused that name but rebuilt everything for ARMv6 to
have software running on Raspberry/Pi 1 and Zero as their SoC had only
armv6 cores.
So you cannot and should not expect binary/toolchain compatibility
between Debian and Raspberry/Pi OS.