[tahoe-dev] Tahoe-LAFS on Fedora 14
Zooko Wilcox-O'Hearn
zooko at zooko.com
Sat Jan 21 21:07:41 UTC 2012
On Fri, Jan 20, 2012 at 12:08 AM, Sameer Verma <sverma at sfsu.edu> wrote:
>
> Tried again with a clean install of OLPC build 11.3.0 (Fedora 14) and
> all the dependencies, but it continues to download
> pycryptopp-0.5.29.tar.gz and then proceed to compile it.
Hm... According to my model of things, it should look here:
https://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/README.html
And since it is Python 2.7, linux, 32-bit x86, then it should find
this file named pycryptopp-0.5.29.post19-py2.7-linux-i686.egg...
Oh, I wonder if it is because your Python says its machine type is
"i386" and that egg says "i686"? Please tell me what is the output on
your OLPC XO1 from:
python misc/build_helpers/show-tool-versions.py | grep
-Ee"^(platform|machine|python)"
The equivalent output from the two machines that I used to build
candidate eggs for pycryptopp for 32-bit x86 were:
https://tahoe-lafs.org/buildbot-pycryptopp/builders/atlas1%20natty%20syslib/builds/17/steps/show-tool-versions/logs/stdio
platform: Linux-2.6.38-11-generic-pae-i686-with-Ubuntu-11.04-natty
machine: i686
python: 2.7.1+ (r271:86832, Apr 11 2011, 18:05:24) [GCC 4.5.2]
https://tahoe-lafs.org/buildbot-pycryptopp/builders/luther%20sid/builds/15/steps/show-tool-versions/logs/stdio
platform: Linux-2.6.37-1-686-i686-with-debian-wheezy-sid
machine: i686
python: 2.7.2+ (default, Jan 13 2012, 23:15:17) [GCC 4.6.2]
Perhaps I should try renaming the egg from "i686" to "i386" like all
the ones in the "Python 2.6" table. I guess I'll try that...
Okay, I did this:
mv pycryptopp-0.5.29.post19-py2.7-linux-i686.egg
pycryptopp-0.5.29.post19-py2.7-linux-i386.egg
Please try again!
Regards,
Zooko
More information about the tahoe-dev
mailing list