Re: python311 vs expat

Jonathan Perkin <[email protected]> Fri, 20 Mar 2026 07:25:20 +0000
Newsgroups gmane.os.netbsd.devel.packages
Message-ID <[email protected]>
* On 2026-03-20 at 06:28 GMT, Adam wrote:

>The problem is, not every operating system provides 'expat_config.h', but pkgsrc thinks the external expat is fine.
>
>The --without-system-expat makes Python use the internal (vendored) expat.
>
>A quick fix would be to make all Python packages force use expat from pkgsrc (see below).
>
>How does that sounds?

I think it's fine for now, given that we're deep into a freeze, as it's 
minimal impact and fixes a top breakage.  The proper fix I think would 
be to add expat_config.h to BUILTIN_FIND_HEADERS, though some may object 
that it harshly penalises these systems.  I don't know their reasoning 
for not providing a full builtin implementation, but one workaround for 
that might be to touch a fake expat_config.h in BUILDLINK_DIR in those 
situations.

-- 
Jonathan Perkin                    pkgsrc.smartos.org
Open Source Complete Cloud   www.tritondatacenter.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.