Hi David,<br> 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".<br>
<br>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:<br>
<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>PyPy used to build correctly but I haven't tried to build it in the last 6 months...<br><br>Gabriel<br><br><div class="gmail_quote">2011/8/15 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 Monday, 15 August 2011 17:30:33 Gabriel Lavoie wrote:<br>
> Hi David,<br>
> for your information, I'm currently trying to make my FreeBSD buildbot<br>
> back online. It broke when the requirement for the "pypy" binary to build<br>
> PyPy appeared. It seems there are still some issues to make PyPy build<br>
> again under FreeBSD. I'll keep you updated.<br>
<br>
</div>Thanks for the update. I have been working on a port for pypy. The code 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 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>
<div><div></div><div class="h5"><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 that<br>
> > > 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 we<br>
> > > 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 support<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>