Zooko O'Whielacronx wrote: > I think you make a good guess. I know that building pycryptopp with > g++ takes a lot of memory. Let's see if we can confirm that this is > what happens, and if this is the problem then the solution is to build > binaries of pycryptopp on a machine with plenty of RAM and upload > those binaries to this tahoe directory [1], which the tahoe build > process searches. > > [1] > http://testgrid.allmydata.org:3567/uri/URI%3ADIR2-RO%3Asnrfwfxatrci35zdgjnzxxx2ke%3Aunarxv347edtku3xzmefy4mcdmfngxzeb72iyqcadbjzjpczjx5a
I built pycryptopp and tahoe on the OLPC (nickname "olpc"). I removed "-Os" from the extra_compile_args in setup.py for pycryptopp. I'm running the same build on the NSLU2, but it's going to take a while. I don't have an armel machine with lots of RAM (I do have a Nokia tablet with 128 MB I can try on). Does anyone know how to get "-O3" and "-g" out of the CFLAGS? They are not in setup.py, it looks like they're getting pulled in from the python distutils defaults. I don't have a write handle to [1], but I'll put the pycryptopp egg up on my web page and send a link [2]. I built pycryptopp with "python setup.py bdist_egg", then put the egg file in dist into the main tahoe directory. Tahoe installed the egg and continued the build process. [2] http://www.hpcf.upr.edu/~humberto/pycryptopp-0.5.10-py2.5-linux-i586.egg _______________________________________________ tahoe-dev mailing list [email protected] http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
