SS20 broke Python?

[Jon Buller <jon%bullers.net@localhost>]

Anyone gotten Python to build on a sparc recently?  I have a SS20 mail
and web server running 4_stable.  I have had Python 2.4 running fine on
it for some time now, but want to upgrade the system to -current (new
postfix, courier-imap -> dovecot, apache -> httpd, etc.)

Every time I have tried to put Python on it, either 2.4, 2.5, or 2.6,
(and I tried on NetBSD 5.0 too) it cores during install like this:

Compiling /usr/pkg/lib/python2.6/test/test_bisect.py ...
Compiling /usr/pkg/lib/python2.6/test/test_bool.py ...
Compiling /usr/pkg/lib/python2.6/test/test_bsddb.py ...
Compiling /usr/pkg/lib/python2.6/test/test_bsddb185.py ...
Compiling /usr/pkg/lib/python2.6/test/test_bsddb3.py ...
Compiling /usr/pkg/lib/python2.6/test/test_buffer.py ...
Compiling /usr/pkg/lib/python2.6/test/test_bufio.py ...
Compiling /usr/pkg/lib/python2.6/test/test_builtin.py ...
[1]   Segmentation fault (core dumped) PYTHONPATH=/usr/...
*** Error code 139

Stop.
make: stopped in /usr/pkgsrc/lang/python26/work/Python-2.6.4
*** Error code 1

Stop.


I gave the python people a GDB trace of the core, but I'm wondering if
something broke in NetBSD somehow, or if I just have some sort of subtly
broken system.  It would be nice to be able to tell the python people
several other people can replicate it.  (Or even "never mind" after I get
the egg off my face.)  BTW, it works fine on my amd64 and sparc64 systems
or I'd be posting on tech-pkg instead of port-sparc.

Jon