Bug#1102074: libstdc++-12-dev: _GLIBCXX_HAVE_ATOMIC_LOCK_POLICY differs between Debian and Raspberry Pi OS (tested on armhf)

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 ht

Bug#1102074: libstdc++-12-dev: _GLIBCXX_HAVE_ATOMIC_LOCK_POLICY differs between Debian and Raspberry Pi OS (tested on armhf)

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 O

Bug#1102074: libstdc++-12-dev: _GLIBCXX_HAVE_ATOMIC_LOCK_POLICY differs between Debian and Raspberry Pi OS (tested on armhf)

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 Boo

Processing of gcc-snapshot_20250404-1_source.changes

gcc-snapshot_20250404-1_source.changes uploaded successfully to localhost along with the files: gcc-snapshot_20250404-1.dsc gcc-snapshot_20250404.orig.tar.gz gcc-snapshot_20250404-1.debian.tar.xz gcc-snapshot_20250404-1_source.buildinfo Greetings, Your Debian queue daemon (running