Re: python

[David Holland <dholland-pkgtech%netbsd.org@localhost>]

On Sun, Sep 16, 2012 at 06:52:02PM +0000, David Holland wrote:
 > On Sun, Sep 16, 2012 at 08:32:47PM +0900, OBATA Akio wrote:
 >  > >So, after the libffi update all five python versions no longer build;
 >  > >something in them dumps core partway through.
 >  > 
 >  > I have no build failure for all five python versions on my
 >  > NetBSD/i386 5.1.2 box.
 > 
 > Ok, it seems to be only my test environment, and it's probably because
 > something in the Python build is mixing $OTHERPREFIX with /usr/pkg.
 > Bleh. But at least it's not a critical problem. 

No, I take it back, it's not my test environment. Nor is it libffi, it
turns out. It works in 6.99.7, fails in 6.99.11, both amd64. I wonder
if it's related to execinfo.

--- python ---
gcc -pthread -L/usr/pkgsrc/lang/python27/work/Python-2.7.3 -L/usr/lib 
-Wl,-R/usr/lib -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -Wl,--export-dynamic -o python 
 Modules/python.o  -L. -lpython2.7 -lpthread  -lutil   -lm  
/usr/pkgsrc/lang/python27/work/Python-2.7.3/libpython2.7.so: warning: warning: 
tmpnam() possibly used unsafely, use mkstemp() or mkdtemp()
/usr/pkgsrc/lang/python27/work/Python-2.7.3/libpython2.7.so: warning: warning: 
tempnam() possibly used unsafely, use mkstemp() or mkdtemp()
--- sharedmods ---
[1]   Segmentation fault      LD_LIBRARY_PATH=...
*** [sharedmods] Error code 139

-- 
David A. Holland
dholland%netbsd.org@localhost