-
Notifications
You must be signed in to change notification settings - Fork 422
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dependency issue with M2Crypto #47
Comments
This is really bad. I'm not sure the install process can be fixed. So I'll look at switching to pyCrypto instead. |
It seems that this happens only when pysaml2 is being installed with pip. The installation from github is satisfied with the preinstalled m2crypt-0.20. But yes, this is a bit weird. Am 08.07.2013 um 17:50 schrieb Roland Hedberg notifications@github.com:
|
Good morning, so you switched already to pycrypto? Am 16.12.2013 um 09:12 schrieb Roland Hedberg notifications@github.com:
|
16 dec 2013 kl. 09:14 skrev Rainer Hörbe notifications@github.com:
Yes, it's in the latest version. -- Roland |
M2Crypto (0.17 up to 0.21) has build issues on Fedora/RHEL/CentOS platforms. The reason seems to be that RH removed EC support from OpenSSL, and M2Crypto/SWIG cannot deal with the modified openssl header files.
The proper way would be to install the OS package for M2Crypto. So 'yum m2crypto' properly installs m2crypto-0.20.2-9.el6.x86_64.
However, pysaml2 (from git) ignores this package and installs M2Crypto-0.21.1. As pip does not know about the platform issues, swig will fail with "This openssl-devel package does not work your architecture?". "uname -m" yields x86_64, but somehow swig seems to be unable to select the proper opensslconf-x86_64.h.
In addition, m2crypto does not resolve the dependencies for swig and openssl-devel, so this must be resolved manually.
Is there an essetial dependency between pysaml2 and M2Crypto-0.21? If yes, can the install process be fixed?
The text was updated successfully, but these errors were encountered: