[pypy-dev] 1.6 status report

Tue Aug 16 06:28:52 CEST 2011

On Tuesday, 16 August 2011 05:50:18 Gabriel Lavoie wrote:
> Hi David,
>      I took a look at your port and it looks good! The patch you made for
> SANDBOX should probably not be needed, with a fix upstream. It seems PyPy
> still have a few "hardcoded path" issues that need to be looked at for
> FreeBSD (and probably for Darwin too for tools like Darwin Ports). I felt
> on one of those issues this morning with "expat.h" and "libexpat.so". The
> translation process didn't look at /usr/local/include and /usr/local/lib
> to find them. Actually, there are a few places where the
> "pypy/translator/platform" module should be use to find include/lib paths.
> I made the initial "freebsd.py" file in there that contains "general"
> references to include/lib directories in "/usr/local".

Thanks, sandbox has not been tested as I do not know how to.  An example 
script that makes sandbox behave like a normal python/pypy instance would be 
nice...

On the expat issue:
# ldd `which pypy1.5`
/usr/local/bin/pypy1.5:
        libm.so.5 => /lib/libm.so.5 (0x801664000)
        libintl.so.9 => /usr/local/lib/libintl.so.9 (0x801885000)
        libssl.so.6 => /usr/lib/libssl.so.6 (0x801a8e000)
        libcrypto.so.6 => /lib/libcrypto.so.6 (0x801ce1000)
        libexpat.so.6 => /usr/local/lib/libexpat.so.6 (0x802082000)
        libbz2.so.4 => /usr/lib/libbz2.so.4 (0x8022a5000)
        libz.so.6 => /lib/libz.so.6 (0x8024b5000)
        librt.so.1 => /usr/lib/librt.so.1 (0x8026cb000)
        libutil.so.9 => /lib/libutil.so.9 (0x8028d0000)
        libffi.so.5 => /usr/local/lib/libffi.so.5 (0x802ae1000)
        libncurses.so.8 => /lib/libncurses.so.8 (0x802ce7000)
        libcrypt.so.5 => /lib/libcrypt.so.5 (0x802f34000)
        libthr.so.3 => /lib/libthr.so.3 (0x803154000)
        libc.so.7 => /lib/libc.so.7 (0x803377000)
        libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x8036bf000)

I also see those error yet it appears expat is picked up somehow, maybe as a 
depenendency?  

> About my current issue, maybe you've seen it. When I try to build PyPy
> using CPython, I get a "Broken Pipe" error and the process fails (using
> the standard "python translate.py -O2" command). Have you seen this
> problem recently? I'm trying with the latest trunk. It seems the "python"
> process runs out of memory as I have this in my kernel log:

I have not encountered that problem before (except I suffer from ENOMEM).

> swap_pager_getswapspace(16): failed
> pid 15107 (cc1), uid 1001, was killed: out of swap space
> swap_pager: out of swap space
> swap_pager_getswapspace(2): failed
> pid 37981 (python), uid 1001, was killed: out of swap space

I have seen this problem before.  FreeBSD hard codes the size of swap it can 
access, and does not adapt it based on RAM or active swap.  To fix that try 
the following in /boot/loader.conf:

# Increase max swap zone to allow for ~64GB of swap                                                                                   
kern.maxswzone="268435456"  # 256MB

> PyPy used to build correctly but I haven't tried to build it in the last 6
> months...

I have successfully built pypy-1.5 and trunk (~1 week ago), so it is possible.  
If you are still having problems please send me the installed physical memory, 
and the output of `swapinfo` and `uname -a`.  

> 2011/8/15 David Naylor <naylor.b.david at gmail.com>
> 
> > On Monday, 15 August 2011 17:30:33 Gabriel Lavoie wrote:
> > > Hi David,
> > > 
> > >     for your information, I'm currently trying to make my FreeBSD
> > 
> > buildbot
> > 
> > > back online. It broke when the requirement for the "pypy" binary to
> > > build PyPy appeared. It seems there are still some issues to make PyPy
> > > build again under FreeBSD. I'll keep you updated.
> > 
> > Thanks for the update.  I have been working on a port for pypy.  The code
> > is
> > at github.com/DragonSA/pypy.  It may be able to help you compile pypy
> > under
> > FreeBSD.  There is a branch called 1.6 that is compatible with trunk.  To
> > compile from 1.6 set WRKSRC to point to a fresh checkout of pypy:
> > 
> > # make install WRKSRC=/path/to/hg/checkout/of/pypy
> > 
> > The master branch uses the 1.5 sources.
> > 
> > > 2011/8/11 David Naylor <naylor.b.david at gmail.com>
> > > 
> > > > On Thursday, 11 August 2011 11:08:18 Maciej Fijalkowski wrote:
> > > > > Hi
> > > > > 
> > > > > A little status update from my side.
> > > > > 
> > > > > I'm trying to get 1.6 out of the door and there are a few things
> > > > > that stand out before we can do it.
> > > > > 
> > > > > * Windows situation (a lot of crashes with missing liveness). Also
> > > > > lib-python tests take 10h which is a bit too much IMO (not a new
> > > > > regression though)
> > > > > * OS X situation (missing buildbots, being addressed now)
> > > > > * A bunch of issues that either should be decided we don't care or
> > > > > we do care and fix it.
> > > > > * Missing jitviewer release/demo that I'm doing right now
> > > > > * Alex reported sqlite crashes
> > > > > * random segfault when running trackgcroot, armin, did you have a
> > > > > look? I can do if you don't
> > > > 
> > > > Would anyone be interested in the FreeBSD situation?  If so what
> > 
> > support
> > 
> > > > do you need?  I am currently updating my repository and will report
> > > > back...
> > > > 
> > > > _______________________________________________
> > > > pypy-dev mailing list
> > > > pypy-dev at python.org
> > > > http://mail.python.org/mailman/listinfo/pypy-dev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20110816/ad50d6ec/attachment-0001.pgp>