[tahoe-dev] Fixed? Freebsd unparsable directory

[zooko]

Dear Ben Hyde:

Thank you for the debugging!  It looks like maybe FreeBSD's g++  
exercises a known bug in pycryptopp which I had previously thought  
wasn't exercised by g++:

http://allmydata.org/trac/pycryptopp/changeset/146/pycryptopp/cipher

You could test this by comparing the self-tests of pycryptopp 0.3.0  
or pycryptopp 0.4.0 (both of which had that bug) with pycryptopp  
0.5.1, which has fixed that bug:

http://pypi.python.org/pypi/pycryptopp

(ben switched from tahoe-1.0.0 to tahoe-1.0.0-r2525, and then:)

> Building with that everything seems to work.

Hm.  This doesn't make sense -- tahoe-1.0.0-r2525 still comes with  
pycryptopp-0.3.0:

http://allmydata.org/trac/tahoe/browser/misc/dependencies?rev=2525

So you should have gotten the same error.

Regards,

Zooko