Okay! It seems I've hit the GCC 4.2 memory usage bug:<br><a href="https://bugs.launchpad.net/ubuntu/+source/gcc-4.2/+bug/187391">https://bugs.launchpad.net/ubuntu/+source/gcc-4.2/+bug/187391</a><br><a href="http://comments.gmane.org/gmane.comp.python.pypy/7634">http://comments.gmane.org/gmane.comp.python.pypy/7634</a><br>
<br>I'm now trying to build with GCC 4.6 (a port is available) and I'll report back.<br><br>Gabriel<br><br><div class="gmail_quote">2011/8/16 David Naylor <span dir="ltr"><<a href="mailto:naylor.b.david@gmail.com">naylor.b.david@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Tuesday, 16 August 2011 05:50:18 Gabriel Lavoie wrote:<br>
> Hi David,<br>
</div><div class="im">> I took a look at your port and it looks good! The patch you made for<br>
> SANDBOX should probably not be needed, with a fix upstream. It seems PyPy<br>
> still have a few "hardcoded path" issues that need to be looked at for<br>
> FreeBSD (and probably for Darwin too for tools like Darwin Ports). I felt<br>
> on one of those issues this morning with "expat.h" and "libexpat.so". The<br>
> translation process didn't look at /usr/local/include and /usr/local/lib<br>
> to find them. Actually, there are a few places where the<br>
> "pypy/translator/platform" module should be use to find include/lib paths.<br>
> I made the initial "freebsd.py" file in there that contains "general"<br>
> references to include/lib directories in "/usr/local".<br>
<br>
</div>Thanks, sandbox has not been tested as I do not know how to. An example<br>
script that makes sandbox behave like a normal python/pypy instance would be<br>
nice...<br>
<br>
On the expat issue:<br>
# ldd `which pypy1.5`<br>
/usr/local/bin/pypy1.5:<br>
libm.so.5 => /lib/libm.so.5 (0x801664000)<br>
libintl.so.9 => /usr/local/lib/libintl.so.9 (0x801885000)<br>
libssl.so.6 => /usr/lib/libssl.so.6 (0x801a8e000)<br>
libcrypto.so.6 => /lib/libcrypto.so.6 (0x801ce1000)<br>
libexpat.so.6 => /usr/local/lib/libexpat.so.6 (0x802082000)<br>
libbz2.so.4 => /usr/lib/libbz2.so.4 (0x8022a5000)<br>
libz.so.6 => /lib/libz.so.6 (0x8024b5000)<br>
librt.so.1 => /usr/lib/librt.so.1 (0x8026cb000)<br>
libutil.so.9 => /lib/libutil.so.9 (0x8028d0000)<br>
libffi.so.5 => /usr/local/lib/libffi.so.5 (0x802ae1000)<br>
libncurses.so.8 => /lib/libncurses.so.8 (0x802ce7000)<br>
libcrypt.so.5 => /lib/libcrypt.so.5 (0x802f34000)<br>
libthr.so.3 => /lib/libthr.so.3 (0x803154000)<br>
libc.so.7 => /lib/libc.so.7 (0x803377000)<br>
libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x8036bf000)<br>
<br>
I also see those error yet it appears expat is picked up somehow, maybe as a<br>
depenendency?<br>
<div class="im"><br>
> About my current issue, maybe you've seen it. When I try to build PyPy<br>
> using CPython, I get a "Broken Pipe" error and the process fails (using<br>
> the standard "python translate.py -O2" command). Have you seen this<br>
> problem recently? I'm trying with the latest trunk. It seems the "python"<br>
> process runs out of memory as I have this in my kernel log:<br>
<br>
</div>I have not encountered that problem before (except I suffer from ENOMEM).<br>
<div class="im"><br>
> swap_pager_getswapspace(16): failed<br>
> pid 15107 (cc1), uid 1001, was killed: out of swap space<br>
> swap_pager: out of swap space<br>
> swap_pager_getswapspace(2): failed<br>
> pid 37981 (python), uid 1001, was killed: out of swap space<br>
<br>
</div>I have seen this problem before. FreeBSD hard codes the size of swap it can<br>
access, and does not adapt it based on RAM or active swap. To fix that try<br>
the following in /boot/loader.conf:<br>
<br>
# Increase max swap zone to allow for ~64GB of swap<br>
kern.maxswzone="268435456" # 256MB<br>
<div class="im"><br>
> PyPy used to build correctly but I haven't tried to build it in the last 6<br>
> months...<br>
<br>
</div>I have successfully built pypy-1.5 and trunk (~1 week ago), so it is possible.<br>
If you are still having problems please send me the installed physical memory,<br>
and the output of `swapinfo` and `uname -a`.<br>
<div><div></div><div class="h5"><br>
> 2011/8/15 David Naylor <<a href="mailto:naylor.b.david@gmail.com">naylor.b.david@gmail.com</a>><br>
><br>
> > On Monday, 15 August 2011 17:30:33 Gabriel Lavoie wrote:<br>
> > > Hi David,<br>
> > ><br>
> > > for your information, I'm currently trying to make my FreeBSD<br>
> ><br>
> > buildbot<br>
> ><br>
> > > back online. It broke when the requirement for the "pypy" binary to<br>
> > > build PyPy appeared. It seems there are still some issues to make PyPy<br>
> > > build again under FreeBSD. I'll keep you updated.<br>
> ><br>
> > Thanks for the update. I have been working on a port for pypy. The code<br>
> > is<br>
> > at <a href="http://github.com/DragonSA/pypy" target="_blank">github.com/DragonSA/pypy</a>. It may be able to help you compile pypy<br>
> > under<br>
> > FreeBSD. There is a branch called 1.6 that is compatible with trunk. To<br>
> > compile from 1.6 set WRKSRC to point to a fresh checkout of pypy:<br>
> ><br>
> > # make install WRKSRC=/path/to/hg/checkout/of/pypy<br>
> ><br>
> > The master branch uses the 1.5 sources.<br>
> ><br>
> > > 2011/8/11 David Naylor <<a href="mailto:naylor.b.david@gmail.com">naylor.b.david@gmail.com</a>><br>
> > ><br>
> > > > On Thursday, 11 August 2011 11:08:18 Maciej Fijalkowski wrote:<br>
> > > > > Hi<br>
> > > > ><br>
> > > > > A little status update from my side.<br>
> > > > ><br>
> > > > > I'm trying to get 1.6 out of the door and there are a few things<br>
> > > > > that stand out before we can do it.<br>
> > > > ><br>
> > > > > * Windows situation (a lot of crashes with missing liveness). Also<br>
> > > > > lib-python tests take 10h which is a bit too much IMO (not a new<br>
> > > > > regression though)<br>
> > > > > * OS X situation (missing buildbots, being addressed now)<br>
> > > > > * A bunch of issues that either should be decided we don't care or<br>
> > > > > we do care and fix it.<br>
> > > > > * Missing jitviewer release/demo that I'm doing right now<br>
> > > > > * Alex reported sqlite crashes<br>
> > > > > * random segfault when running trackgcroot, armin, did you have a<br>
> > > > > look? I can do if you don't<br>
> > > ><br>
> > > > Would anyone be interested in the FreeBSD situation? If so what<br>
> ><br>
> > support<br>
> ><br>
> > > > do you need? I am currently updating my repository and will report<br>
> > > > back...<br>
> > > ><br>
> > > > _______________________________________________<br>
> > > > pypy-dev mailing list<br>
> > > > <a href="mailto:pypy-dev@python.org">pypy-dev@python.org</a><br>
> > > > <a href="http://mail.python.org/mailman/listinfo/pypy-dev" target="_blank">http://mail.python.org/mailman/listinfo/pypy-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Gabriel Lavoie<br><a href="mailto:glavoie@gmail.com">glavoie@gmail.com</a><br>