-
Notifications
You must be signed in to change notification settings - Fork 204
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
problem building MySQL-python python extension with rpath #2054
Comments
@pescobar The lack of an actual error message for the failing import is weird, but it seems like this is a segmentation fault, cfr. http://stackoverflow.com/questions/24139389/unable-to-find-out-what-return-code-of-11-means. Figuring this one out may be very difficult, this is a good candidate for using the |
@boegel that's what I have done by now but I wanted to report the problem. What puzzles me a little bit are these lines:
This extension is using these options:
Maybe the sanity check is having any problem when using the |
@pescobar the failure to import Not sure what is causing the segfault though... |
The build completes but the rpath sanity check fails. Here you can see the build log
https://gist.github.com/9cc52d50d238aee59e724522b1adcc8f
The important lines seem these but I don't get the reason why it's failing. Any idea? Why this line?
Failed to import module 'easybuild.easyblocks.mysql_python': No module named mysql_python
The text was updated successfully, but these errors were encountered: