Re: python313 (2025Q4) fails to build (link) on hppa -current

●To: maya%netbsd.org@localhost, pkgsrc-users%netbsd.org@localhost ●Subject: Re: python313 (2025Q4) fails to build (link) on hppa -current ●From: Brandon Applegate <vom513%gmail.com@localhost> ●Date: Wed, 31 Dec 2025 11:01:30 -0500

Thanks for the reply and info. As you stated - "not a full fix" - adding this still results in the link failure at the end. I verified that the configure option made it in:

c3700# grep mimalloc work/Python-3.13.11/config.status | head -1
ac_cs_config='--enable-shared --with-openssl=/usr --without-ensurepip --without-system-expat --with-mimalloc=no ac_cv_header_uuid_h=false --without-pymalloc --with-readline=readline --prefix=/usr/pkg --build=hppa--netbsd --host=hppa--netbsd --mandir=/usr/pkg/man --enable-option-checking=yes build_alias=hppa--netbsd host_alias=hppa--netbsd PKG_CONFIG=/usr/pkgsrc/lang/python313/work/.tools/bin/pkg-config PKG_CONFIG_PATH= PKG_CONFIG_LIBDIR=/usr/pkgsrc/lang/python313/work/.buildlink/lib/pkgconfig:/usr/pkgsrc/lang/python313/work/.buildlink/share/pkgconfig CC=gcc '\''CFLAGS=-O2 -I/usr/include -I/usr/pkg/include'\'' '\''LDFLAGS=-L/usr/lib -Wl,-R/usr/lib -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -latomic -L/usr/X11R7/lib -Wl,-R/usr/X11R7/lib'\'' LIBS=-lcrypt '\''CPPFLAGS=-I/usr/include -I/usr/pkg/include'\'''

An example compile line mentions including from "Include/internal/mimalloc" but perhaps that's intended (I'm way out of my depth here...):

gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -O2 -I/usr/include -I/usr/pkg/include -O2 -I/usr/include -I/usr/pkg/include -O2 -I/usr/include -I/usr/pkg/include -std=gnu11 -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -Wstrict-prototypes -Werror=implicit-function-declaration -f
visibility=hidden -I./Include/internal -I./Include/internal/mimalloc -I. -I./Include -I/usr/include -I/usr/pkg/include -I/usr/include -I/usr/pkg/include -fPIC -DPy_BUILD_CORE_BUILTIN -c ./Modules/pwdmodule.c -o Modules/pwdmodule.o

On Tue, Dec 30, 2025 at 4:13 PM <maya%netbsd.org@localhost> wrote:

For some context but not a full fix, python 3.13 introduced a new default-on-if-you-have-stdatomic.h allocator, mimalloc. You can opt out of it with the addition of the following line along other CONFIGURE_ARGS in lang/python313/Makefile: CONFIGURE_ARGS+= --with-mimalloc=no mimalloc seems to require 64 bit atomics, which hppa definitely doesn't have as instructions, so it relies on a library implementation which uses locking. Something seems to be going wrong with whoever is supposed to be supplying __sync_fetch_and_add_8. Maybe NetBSD should be doing it in libc for hppa (and sparc) and not need libatomic here? It's also unclear why libatomic is not providing it (it seems these definitions come from libgcc, not libatomic?)

●References: ●python313 (2025Q4) fails to build (link) on hppa -current ●From: vom513 ●Re: python313 (2025Q4) fails to build (link) on hppa -current ●From: maya

●Prev by Date: Re: Update of wip/sddm to version 0.21 ●Next by Date: Re: Bob v0.1.0 ready for beta testing ●Previous by Thread: Re: python313 (2025Q4) fails to build (link) on hppa -current ●Next by Thread: Re: python313 (2025Q4) fails to build (link) on hppa -current ●Indexes: ● reverse Date ● reverse Thread ● Old Index Home | Main Index | Thread Index | Old Index