From: Glyph L. <gl...@tw...> - 2010-10-08 23:51:58
|
On Oct 7, 2010, at 11:27 PM, ex...@tw... wrote: > I've just uploaded a number of 0.11a1 release files. You can find them > on <http://launchpad.net/pyopenssl>. Congrats, this sounds like it's shaping up to be a great release. > Please give it a spin and let me know how it goes. Well, checking out from 'lp:~exarkun/pyopenssl/release-0.11', everything works great. But, if I actually download the release tarball from <http://launchpad.net/pyopenssl/main/0.11a1/+download/pyOpenSSL-0.11a1.tar.gz>, 'python.setup.py build' yields this: gcc-4.2 -fno-strict-aliasing -fno-common -dynamic -DNDEBUG -g -fwrapv -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch i386 -arch ppc -arch x86_64 -pipe -I/System/Library/Frameworks/Python.framework/Versions/2.6/include/python2.6 -c OpenSSL/crypto/crypto.c -o build/temp.macosx-10.6-universal-2.6/OpenSSL/crypto/crypto.o OpenSSL/crypto/crypto.c:15:20: error: crypto.h: No such file or directory OpenSSL/crypto/crypto.c:16:20: error: pkcs12.h: No such file or directory and the predictable follow-on cascade or errors. I got this on both OS X Snow Leopard and Ubuntu Lucid. |