Heikki Toivonen wrote:
John Nagle wrote:
The right question is "uname --hardware-platform". That returns "i386" if
running on something emulating a 386, even it it's 64-bit capable.
Thanks, I'll make a note that I'll need to clarify that part.
With that change, the build runs to completion
John Nagle wrote:
> The right question is "uname --hardware-platform". That returns "i386" if
> running on something emulating a 386, even it it's 64-bit capable.
Thanks, I'll make a note that I'll need to clarify that part.
> With that change, the build runs to completion and and the regression
Heikki Toivonen wrote:
John Nagle wrote:
M2Crypto, from
http://pypi.python.org/packages/source/M/M2Crypto/M2Crypto-0.20.1.tar.gz
won't build on Red Hat Linux / 386. The error is
It's some incompatibility between Red Hat include file packaging and
M2Crypto.
Yup, all Fedora Core-based system
John Nagle wrote:
> M2Crypto, from
>
> http://pypi.python.org/packages/source/M/M2Crypto/M2Crypto-0.20.1.tar.gz
>
> won't build on Red Hat Linux / 386. The error is
>
> It's some incompatibility between Red Hat include file packaging and
> M2Crypto.
Yup, all Fedora Core-based systems actually.
M2Crypto, from
http://pypi.python.org/packages/source/M/M2Crypto/M2Crypto-0.20.1.tar.gz
won't build on Red Hat Linux / 386. The error is
swig -python -I/usr/local/include/python2.5 -I/usr/include -includeall -o
SWIG/_m2crypto_wrap.c
SWIG/_m2crypto.i
/usr/include/openssl/opensslconf.h:27: Er
