fix the build on OpenBSD

[zooko]

kyle@… had to patch pycryptopp to get it to build with the -fPIC-compatible version of libgcc, if I understand correctly:

​http://allmydata.org/pipermail/tahoe-dev/2009-November/003132.html

We will need an OpenBSD buildbot to test his patch and to make sure that future changes to pycryptopp don't cause its compatibility with OpenBSD to regress.

[joe]

I am not the original poster, but I had the same issue. The basic problem turns out that if you are linking things on OpenBSD compiled with -fpic you also need to specify -fpic at link time. Therefore, this seems to resolve the problem:

diff -rN old-trunk/setup.py new-trunk/setup.py
60a61,62

extra_link_args.append("-fpic")

The resulting pycryptopp dropped in the right place causes a build of tahoe to succeed, and that build passes all tests.

My thanks to the helpful directions on how to rebuilt the pycryptopp egg and put it in the right place for tahoe, as otherwise this would have been much more painful to figure out.

[zooko]

Hey, thanks joe! So I wonder if we should add extra_link_args.append("-fpic") in all cases or only in case the platform is OpenBSD. I guess I'll wait til we have an OpenBSD buildslave (hint hint) and then try it and see what works.

[zooko]

Okay we have an OpenBSD buildslave:

​http://allmydata.org/buildbot-pycryptopp/builders/Kyle%20OpenBSD-4.6-amd64

Now we just need an OpenBSD hacker to submit a patch so we can see if it fixes the build on the OpenBSD buildslave while not breaking the build on any other platform.

[kmarkley86]

Fix

[kmarkley86]

I've attached a patch that should fix this.

[zooko]

Fixed by [20091214212406-f56e6-fd26ce05422701959d630c92cfa43301777ec124]. Thanks, Kyle!