On Sun, Nov 14, 2010 at 12:48 PM, Scott Dial <[email protected]> wrote: > > (Hi, I'm new to the list.. *waves*)
Welcome! :-) > Eventually I tracked it down to the pycryptoopp binary egg: ... > This is a fully updated CentOS 5 box. Whoever built your > pycryptopp-0.5.25_r755-py2.5-linux-i686.egg ended up linking against a > newer ABI than what a lot of people will have, which is not the best > idea if you are going for "ease of setup" (i.e., none of my production > equipment are running that new of a version of libstdc++). Hm, we have a CentOS 5 buildslave to keep track of these things for us... http://tahoe-lafs.org/buildbot/builders/FreeStorm%20CentOS5-i386 Oh! You have Python 2.5, but the CentOS 5 buildslave (operated by FreeStorm) has Python 2.4. You can find out what version of Python it has by scanning through this noisy output: http://tahoe-lafs.org/buildbot/builders/FreeStorm%20CentOS5-i386/builds/237/steps/show-tool-versions/logs/stdio Or notice the 'py2.4.3' in this summary: http://tahoe-lafs.org/buildbot/builders/FreeStorm%20CentOS5-i386/builds/237/steps/show-tool-versions So, are you running a non-standard version of Python there? Thanks! Regards, Zooko _______________________________________________ tahoe-dev mailing list [email protected] http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
