Re: Various py-* packages missing atomic64.mk

[Greg Troxel <gdt%lexort.com@localhost>]

Havard Eidnes <he%NetBSD.org@localhost> writes:

> a review of the state of my bulk build host for NetBSD/macppc
> 10.0 reveals that all the following packages have failed to build
> because -latomic could not be found:
>
> py310-rapidfuzz-3.10.1/build.log
> py311-rapidfuzz-3.10.1/build.log
> py312-rapidfuzz-3.10.1/build.log
> py313-Pillow-11.0.0/build.log
> py313-brotli-1.1.0/build.log
> py313-cffi-1.17.1/build.log
> py313-cython-3.0.11/build.log
> py313-genshi-0.7.9/build.log
> py313-lxml-5.3.0nb3/build.log
> py313-markupsafe-3.0.2/build.log
> py313-psycopg2-2.9.10/build.log
> py313-rapidfuzz-3.10.1/build.log
> py313-wrapt-1.17.0/build.log
> py313-zope.interface-7.2/build.log
> py313-zopfli-0.2.3/build.log
>
> This is fixable by adding an include of ../../mk/atomic64.mk.

It seems that this is a small subset of python modules, so anything
about 'all python' is wrong.

Do you believe that these have modules implemented in C that uses
atomics?

Do you understand why rapidfuzz is ok on 313 (or is it)?

Do you understand why everything else fails on 313, and is, presumably,
ok on 310/311/312?

Do you expect that these build problems would occur on all 32-bit CPUs,
or do you think this is somehow special to macppc?

(Not arguing against a fix -- just trying to understand more clearly.)