https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119627
Andrew Sayers <gcc.gnu.org at pileofstuff dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|INVALID |FIXED
--- Comment #4 from Andrew Sayers <gcc.gnu.org at pileofstuff dot org> ---
Aha, you're right. _Lock_policy is defined in
/usr/include/c++/12/ext/concurrence.h, based on
_GLIBCXX_HAVE_ATOMIC_LOCK_POLICY.
_GLIBCXX_HAVE_ATOMIC_LOCK_POLICY is enabled in
/usr/arm-linux-gnueabihf/include/c++/12/arm-linux-gnueabihf/bits/c++config.h in
Debian but commented out in Raspberry Pi OS.
I guess this will turn out to be some weird deliberate incompatibility between
the two bookworm's, but at least now I've got a new wall to bang my head
against.
Thanks!
