On Thu, Jul 15, 2010 at 3:03 PM, Adam Mercer <ramer...@gmail.com> wrote: > On Thu, Jul 15, 2010 at 14:10, John Nagle <na...@animats.com> wrote: >> I had a similar problem back in 2007. See >> >> http://bytes.com/topic/python/answers/613336-more-m2crypto-build-problems >> >> Also see >> >> http://bytes.com/topic/python/answers/711381-m2crypto-0-18-new-version-same-old-build-bugs >> >> There have been problems with SWIG. There have been problems with >> how OpenSSL was built (with or without elliptic curve crypto support). >> And there were some issues with building on 64-bit hardware running >> 32-bit operating systems, because the build script was checking >> the wrong system configuration parameter. >> >> Not sure what problem you're having with Mac OS X. From the >> errors, though, I suspect that not all the components involved >> are consistent with 32/64 bit width. > > Thanks, I'm sure everything is consistent with the architecture, i.e. > everything is 64 bit. The last time I build M2Crypto on this box was > against SWIG-1.3.x and OpenSSL-0.9.8? So one of these (or both) has > broken something... Looks like I'll have to revert each one at a > time... > > Cheers > > Adam
The move to 1.0 was a PITA for me, although I appreciate the improved EVP_PKEY support it will probably break a chunk of code. Geremy Condra -- http://mail.python.org/mailman/listinfo/python-list
