Dear Sameer: I've written a FAQ about the build system which names the six libraries that are needed and explains how you could possibly get them from "yum install" or else build them as "Python eggs":
https://tahoe-lafs.org/trac/tahoe-lafs/wiki/CompileError https://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/README.html To find out what row of that matrix matches the XO-1, run: python -c 'import distutils.util;print distutils.util.get_platform();import distutils.sysconfig;print distutils.sysconfig.get_python_version()' You earlier reported: platform: Linux-2.6.35.13_xo1-20111005.1403.olpc.c2bd7b9-i586-with-fedora-11-based_on_Fedora_14 machine: i586 python: 2.7 (r27:82500, Sep 16 2010, 18:03:06) [GCC 4.5.1 20100907 (Red Hat 4.5.1-3)] Since the machine type is "i586" instead of "i686", I suspect that may be why the OLPC builds don't use the "linux-x86" packages offered from the tahoe-lafs-dep-eggs directory. Maybe we could build some packages with "i586" (by building them on the OLPC 1.5) and make a new row on that matrix. Regards, Zooko _______________________________________________ tahoe-dev mailing list [email protected] https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
