M2Crypto doesn't install in venv, or swig doesn't define __x86_64__ which breaks compiling against OpenSSL

Question

I'm trying to install the Python M2Crypto package into a virtualenv on an x86_64 RHEL 6.1 machine. This process invokes swig, which fails with the following error:

$ virtualenv -q --no-site-packages venv
$ pip install -E venv M2Crypto==0.20.2
Downloading/unpacking M2Crypto==0.20.2
  Downloading M2Crypto-0.20.2.tar.gz (412Kb): 412Kb  downloaded
  Running setup.py egg_info for package M2Crypto
Installing collected packages: M2Crypto
  Running setup.py install for M2Crypto
    building 'M2Crypto.__m2crypto' extension
    swigging SWIG/_m2crypto.i to SWIG/_m2crypto_wrap.c
    swig -python -I/usr/include/python2.6 -I/usr/include -includeall -o SWIG/_m2crypto_wrap.c SWIG/_m2crypto.i
    /usr/include/openssl/opensslconf.h:31: Error: CPP #error ""This openssl-devel package does not work your architecture?"". Use the -cpperraswarn option to continue swig processing.
    error: command 'swig' failed with exit status 1
    Complete output from command /home/lorin/venv/bin/python -c "import setuptools;__file__='/home/lorin/venv/build/M2Crypto/setup.py';exec(compile(open(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --single-version-externally-managed --record /tmp/pip-BFiNtU-record/install-record.txt --install-headers /home/lorin/venv/include/site/python2.6:

I've got OpenSSL 1.0.0 installed via RPM packages from RedHat.

The part of /usr/include/openssl/opensslconf.h that causes the error looks like this:

#if defined(__i386__)
#include "opensslconf-i386.h"
#elif defined(__ia64__)
#include "opensslconf-ia64.h"
#elif defined(__powerpc64__)
#include "opensslconf-ppc64.h"
#elif defined(__powerpc__)
#include "opensslconf-ppc.h"
#elif defined(__s390x__)
#include "opensslconf-s390x.h"
#elif defined(__s390__)
#include "opensslconf-s390.h"
#elif defined(__sparc__) && defined(__arch64__)
#include "opensslconf-sparc64.h"
#elif defined(__sparc__)
#include "opensslconf-sparc.h"
#elif defined(__x86_64__)
#include "opensslconf-x86_64.h"
#else
#error "This openssl-devel package does not work your architecture?"
#endif

gcc has the right variable defined:

$ echo | gcc -E -dM - | grep x86_64
#define __x86_64 1
#define __x86_64__ 1

But apparenty swig doesn't, since this is the line that's failing:

swig -python -I/usr/include/python2.6 -I/usr/include -includeall -o \
  SWIG/_m2crypto_wrap.c SWIG/_m2crypto.i

Is there a way to fix this by changing something in my system configuration? M2Crypto gets installed in a virtualenv as part of a larger script I don't control, so avoiding mucking around with the M2Crypto files would be a good thing.

There is [`fedora_setup.sh`](http://svn.osafoundation.org/m2crypto/trunk/fedora_setup.sh) but it requires mucking around with the M2Crypto files. — jfs, Oct 15 '11 at 03:50
@J.F.Sebastian: Not familiar with that, can you provide more details in a complete answer? — Lorin Hochstein, Oct 15 '11 at 23:08

score 26 · Accepted Answer · answered Oct 21 '11 at 20:57

26

M2Crypto supplies a fedora_setup.sh script to handle the problems with Fedora/RL/CentOs releases, but pip, of course, doesn't know anything about it.

After the pip install fails, it leaves the downloaded stuff in the venv/build/M2Crypto directory. do this:

cd <path-to-your-venv>/venv/build/M2Crypto
chmod u+x fedora_setup.sh
./fedora_setup.sh build
./fedora_setup.sh install

This has worked in my install process

answered Oct 21 '11 at 20:57

Pamela McA'Nulty

306
3
4

4

As of today (version 1.5.6) pip cleans up the build directory, so there's nothing to do therein anymore. – Peterino Nov 11 '14 at 20:30

score 11 · Answer 2 · edited Oct 26 '13 at 22:11

11

You just don't have swig installed.

Try:

sudo yum install swig

And then:

sudo easy_install M2crypto

edited Oct 26 '13 at 22:11

Diosney

10,520
15
66
111

answered Oct 26 '13 at 21:51

LeoC

129
1
2

On Mac OS X 10.9.4 I installed swig using MacPorts (`sudo port install swig`). I also had to install Python's markupsafe globally (`sudo pip install markupsafe`), because swig depends on it (`.../markupsafe/_speedups.so: Error opening or reading file`). – Peterino Nov 11 '14 at 20:28
Looks like with MacPorts we also need to install swig-python (`sudo port install swig-python`). – Peterino Nov 11 '14 at 20:44
This worked for me when I had a similar problem on Ubuntu (though of course using apt-get instead of yum). – user3614014 Jan 16 '15 at 13:03

score 9 · Answer 3 · answered Nov 19 '14 at 08:38

9

I did this and it works very well :

env SWIG_FEATURES="-cpperraswarn -includeall -I/usr/include/openssl" pip install M2Crypto

Of course you have to install swigg with sudo yum install swig before

answered Nov 19 '14 at 08:38

chocobn69

175
1
7

score 5 · Answer 4 · answered Oct 17 '12 at 13:32

5

If you are seeing this and are on Ubuntu, use apt-get instead of pip to avoid this issue.
apt-get install python-m2crypto

answered Oct 17 '12 at 13:32

nknj

2,436
5
31
45

score 5 · Answer 5 · edited Jul 24 '14 at 14:26

5

I had a similar issue where /usr/include/openssl was missing opensslconf.h (source https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733644#10)

sudo ln -s /usr/include/x86_64-linux-gnu/openssl/opensslconf.h /usr/include/openssl

edited Jul 24 '14 at 14:26

Aleksei Zyrianov

2,294
1
24
32

answered Jul 24 '14 at 14:13

evendiagram

402
4
6

score 4 · Answer 6 · answered Apr 29 '13 at 12:46

4

There's a repository where "pip install" works:

https://github.com/martinpaljak/M2Crypto

answered Apr 29 '13 at 12:46

Martin Paljak

4,119
18
20

You could try this: pip install git+https://github.com/martinpaljak/M2Crypto.git As I'm planning to wrap up some changes to M2Crypto that are floating around into new release(s) that will end up in pypi, you can safely use the same git tree at the moment. – Martin Paljak Apr 30 '13 at 17:29
1

"pip install git+github.com/martinpaljak/M2Crypto.git" fails with "ValueError: ('Expected version spec in', 'git+github.com/martinpaljak/M2Crypto.git', 'at', '+github.com/martinpaljak/M2Crypto.git')" on my Ubuntu 10.04 system. – Paul Whipp Jun 13 '13 at 07:45
The formatting. Do add https and colons and slashes in front of github.com – Martin Paljak Jun 17 '13 at 13:30
Thanks for this, this is supremely helpful for keeping our build process sane. – Andrew Roberts Jul 24 '13 at 15:52
This doesn't work for a virtual environment on Ubuntu. – Seth Jan 09 '14 at 13:45
Which ubuntu? Will try in a sec. – Martin Paljak Jan 09 '14 at 14:48
Try now. https://github.com/martinpaljak/M2Crypto/commit/134e1d9e7dde2e63064afa2f7ef82df8107889ea should fix it. – Martin Paljak Jan 14 '14 at 12:42

score 3 · Answer 7 · answered Mar 12 '13 at 22:19

3

sudo yum install m2crypto

worked for me to get around this problem.

answered Mar 12 '13 at 22:19

Matt

746
6
16

hahakubile · Answer 8 · 2014-01-10T08:17:01.007

2

I found a new way to fix this problem in centos5.8, try it.

vim setup.py

def finalize_options(self):
  ...
  self.swig_opts.append('-includeall') # after this line
  self.swig_opts.append('-I/usr/include/openssl') # add here

then python setup.py install will work.

edited Jan 10 '14 at 08:17

answered Jan 10 '14 at 08:07

hahakubile

6,978
4
28
18

score 0 · Answer 9 · answered Sep 04 '17 at 21:17

On FreeBSD I had to install Swig (the obvious part) as well (by sudo pkg install swig), but Swig 2.0 executable was named swig2.0 and handle swig resulted in command not found. Solution: symlink Swig 2.0 to handle swig:

ln -s /usr/local/bin/swig2.0 /usr/local/bin/swig

score 0 · Answer 10 · answered Dec 17 '21 at 20:45

0

It seems like not having swig is the problem, as @LeoC said.

For those on MacOS, I'd recommend downloading swig via a package manager like homebrew because it's cleaner.

I.e. you'd run

brew install swig

answered Dec 17 '21 at 20:45

Don Assamongkol

5
1
5

M2Crypto doesn't install in venv, or swig doesn't define __x86_64__ which breaks compiling against OpenSSL

10 Answers10

Linked