Hi!
On Tue, 2023-07-18 09:35:02 +0100, David Brownlee <abs%netbsd.org@localhost> wrote:
> On Tue, 18 Jul 2023 at 09:05, Jan-Benedict Glaw <jbglaw%lug-owl.de@localhost> wrote:
> > 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?
./lib/libm/Makefile:
326 .if (${LIBC_MACHINE_ARCH} == "vax")
327 SRCS= ${NOIEEE_SRCS} ${NOIEEE_ARCH}
328 .else
329 SRCS= ${COMMON_SRCS}
330 .endif
331
332 .ifdef ARCH_ADDS
333 SRCS+= ${ARCH_ADDS}
334 .endif
...and `nextafter` belongs to ${COMMON_SRCS} and is IEEE754 specific.
So I wonder: Should we implement a VAX version? Can probably be done,
though some care must be taken as D- and G-float can, in theory, be
choosen as a gcc command line option. Or drop the declaration?
Another route could be to accept that VAX FP is too dead and go for
soft float all the way. :-/
MfG, JBG
--
Attachment:
signature.asc
Description: PGP signature