Re: pkgsrc: python310 issues -> no ca-certificates

[David Brownlee <abs%netbsd.org@localhost>]

On Tue, 18 Jul 2023 at 09:05, Jan-Benedict Glaw <jbglaw%lug-owl.de@localhost> wrote:
>
> Hi!
>
> Without expecting much of an issue there, I tried to build
> security/ca-certificates, which in turn depends on Python3.
>
>   Python 3.10 is pulled in as a dependency, but fails checking for
> floating point endianess, so I preliminarily fixed that by
>
>         CONFIGURE_ENV+=               ax_cv_c_float_words_bigendian=no
>
>   Interestingly, it breaks later on with a missing nextafter():
>
> gcc -pthread -shared -L. -L/usr/lib -Wl,-R/usr/lib -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -L/usr/X11R7/lib -Wl,-R/usr/X11R7/lib -L/usr/lib -Wl,-R/usr/lib -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -L/usr/X11R7/lib -Wl,-R/usr/X11R7/lib -L/usr/lib -Wl,-R/usr/lib -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -L/usr/X11R7/lib -Wl,-R/usr/X11R7/lib -O2 -O0 -D_FORTIFY_SOURCE=2 -I/usr/include -I/usr/pkg/include -I/usr/include -I/usr/pkg/include build/temp.netbsd-10.99.5-vax-3.10/usr/pkgsrc/lang/python310/work/Python-3.10.12/Modules/_ctypes/_ctypes.o build/temp.netbsd-10.99.5-vax-3.10/usr/pkgsrc/lang/python310/work/Python-3.10.12/Modules/_ctypes/callbacks.o build/temp.netbsd-10.99.5-vax-3.10/usr/pkgsrc/lang/python310/work/Python-3.10.12/Modules/_ctypes/callproc.o build/temp.netbsd-10.99.5-vax-3.10/usr/pkgsrc/lang/python310/work/Python-3.10.12/Modules/_ctypes/cfield.o build/temp.netbsd-10.99.5-vax-3.10/usr/pkgsrc/lang/python310/work/Python-3.10.12/Modules/_ctypes/stgdict.o -L. -L/usr/lib -L/usr/pkg/lib -Wl,-R/usr/X11R7/lib -lffi -o build/lib.netbsd-10.99.5-vax-3.10/_ctypes.so
> *** WARNING: renaming "math" since importing it failed: /usr/pkgsrc/lang/python310/work/Python-3.10.12/build/lib.netbsd-10.99.5-vax-3.10/math.so: Undefined PLT symbol "nextafter" (symnum = 19)
> *** Signal 4

nextafter(3) should be in libm - does that line work with -lm at the end?

>   I also found that CPython 3.11 seems to have dropped support for
> non-IEEE-754 systems. (Whatever that means: I haven't checked in
> detail.) It seems that with 3.10, there's not too much in the way of
> getting something to work, and if we want to keep Python (which
> unfortunately is quite widely used these days, even for quite basic
> stuff like formatting some x509 certs), we'd fix libm and also check
> for newer versions.

That's... annoying with 3.11, but it should be worth getting 3.10
working if we can (thanks for poking at it :)

David