Re: Build failures on 16.x

Colin Percival wrote:
> Hi Python people,
> 
> Most of the 16.x weekly snapshot builds failed with errors rhyming with:
> 
>> pkg-static: Unable to access file /tmp/ports/usr/ports/lang/python311/ 
>> work/stage/usr/local/lib/python3.11/__pycache__/ 
>> _sysconfigdata__freebsd16_.cpython-311.opt-1.pyc:No such file or 
>> directory
>> pkg-static: Unable to access file /tmp/ports/usr/ports/lang/python311/ 
>> work/stage/usr/local/lib/python3.11/__pycache__/ 
>> _sysconfigdata__freebsd16_.cpython-311.opt-2.pyc:No such file or 
>> directory
>> pkg-static: Unable to access file /tmp/ports/usr/ports/lang/python311/ 
>> work/stage/usr/local/lib/python3.11/__pycache__/ 
>> _sysconfigdata__freebsd16_.cpython-311.pyc:No such file or directory
>> pkg-static: Unable to access file /tmp/ports/usr/ports/lang/python311/ 
>> work/stage/usr/local/lib/python3.11/_sysconfigdata__freebsd16_.py:No 
>> such file or directory
> 
> I don't know if this is simply because the python port doesn't know about
> FreeBSD 16.0-CURRENT yet or if it's caused by cross-building from a 15.x
> host; can someone take a look?
> 
Smells like the latter. There's not really too much in CPython itself 
that overtly discriminates between specific base system versions.

-- 
Charlie Li
...nope, still don't have an exit line.