tech-pkg archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: python, expat
Greg Troxel <gdt%lexort.com@localhost> writes:
> In lang/python313, there is
>
> .if ${OPSYS} == NetBSD && ${OPSYS_VERSION} < 119905
> PREFER.expat= pkgsrc # needs expat_config.h
> .endif
>
> However, netbsd-10 has expat_config.h, mod date in 2022.
Looking harder, there was context in the commit message that wasn't
present as a comment in the Makefile. I now believe that
- the version of expat in NetBSD 10 has always been good enough
- NetBSD's install process erroneously did not install expat_config.h
- a pullup to do the install happened recently
That leaves us either solving Problem A or B:
A) all of
- 1) OR
+ i) adjust patterns in python3
+ ii) adjust expat's builtin.mk to accept builtin expat.h only if
expat_config.h is present. Just adding expat_config.h to the
header variable does not work.
- 2) do bulk builds for pkgsrc users with netbsd-10 from after the
pullup
B)
- 1) python, when built with pkgsrc expat, appears to crash during xml
operations (qgis plugin loading). Based on struggling with macOS,
I see that there are multiple -I args and suspect this results in
the build seeing some mix of expat versions -- but I'm guessing.
Fix this.
Personally, I've done A)1)i) and A)2) locally, so programs run ok for
me, but that's not going to help other people.
Home |
Main Index |
Thread Index |
Old Index