Skip to content
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

Open
pescobar opened this issue Dec 10, 2016 · 3 comments
Open

problem building MySQL-python python extension with rpath #2054

pescobar opened this issue Dec 10, 2016 · 3 comments
Milestone

Comments

@pescobar
Copy link
Member

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

== 2016-12-10 19:50:41,638 run.py:137 DEBUG run_cmd: running cmd python -c "import MySQLdb" (in /scicore/home/scicore/easybuild/easyconfigs)
== 2016-12-10 19:50:41,755 run.py:433 DEBUG cmd "python -c "import MySQLdb"" exited with exitcode -11 and output:

== 2016-12-10 19:50:41,755 easyblock.py:1277 INFO exts_filter result  -11
== 2016-12-10 19:50:41,756 easyblock.py:1279 INFO Not skipping MySQL-python
== 2016-12-10 19:50:41,756 easyblock.py:1280 DEBUG exit code: -11, stdout/err: 
== 2016-12-10 19:50:41,757 easyblock.py:1674 DEBUG Installing extensions
== 2016-12-10 19:50:41,757 easyblock.py:1698 DEBUG Starting extension MySQL-python
== 2016-12-10 19:50:41,759 easyconfig.py:1100 DEBUG Failed to import module 'easybuild.easyblocks.mysql_python': No module named mysql_python
== 2016-12-10 19:50:41,759 easyconfig.py:1106 DEBUG No module path 'easybuild.easyblocks.mysql_python' found
== 2016-12-10 19:50:41,760 easyconfig.py:1108 DEBUG Module path determined based on software name: easybuild.easyblocks.mysql_python
== 2016-12-10 19:50:41,760 easyconfig.py:1114 DEBUG getting class for easybuild.easyblocks.mysql_python.EB_MySQL_minus_python
== 2016-12-10 19:50:41,762 easyconfig.py:1121 DEBUG error regexp: No module named mysql_python
== 2016-12-10 19:50:41,763 easyconfig.py:1142 DEBUG No class found for easyblock 'None' (software name 'MySQL-python', default fallback: False
== 2016-12-10 19:50:41,763 easyblock.py:1714 DEBUG Obtained class None for extension MySQL-python
== 2016-12-10 19:50:41,765 easyblock.py:1736 DEBUG Obtained class <class 'easybuild.easyblocks.generic.pythonpackage.PythonPackage'> for installing extension MySQL-python```
@boegel
Copy link
Member

boegel commented Dec 10, 2016

@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 rpath toolchain option I think... ;-)

@boegel boegel added this to the 3.1.0 milestone Dec 10, 2016
@pescobar
Copy link
Member Author

@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:

DEBUG run_cmd: running cmd python -c "import MySQLdb" (in /scicore/home/scicore/easybuild/easyconfigs)

DEBUG Failed to import module 'easybuild.easyblocks.mysql_python': No module named mysql_python

This extension is using these options:

    ('MySQL-python', '1.2.5', {
        'source_urls': ['https://pypi.python.org/packages/source/M/MySQL-python/'],
        'modulename': 'MySQLdb',
        'source_tmpl': 'MySQL-python-1.2.5.zip',
    }),

Maybe the sanity check is having any problem when using the modulename option for an extension?

@boegel
Copy link
Member

boegel commented Jan 14, 2017

@pescobar the failure to import mysql_python is normal, that's just EasyBuild looking for a dedicated easyblock to build & install the mysql-python extension with (but there is none, so it'll fall back to PythonPackage)

Not sure what is causing the segfault though...

@boegel boegel modified the milestone: 3.1.0 Jan 14, 2017
@boegel boegel added this to the 3.2.0 milestone Feb 28, 2017
@boegel boegel modified the milestones: 3.2.0, 3.3.0 May 2, 2017
@boegel boegel modified the milestones: 3.3.0, 3.x Jun 22, 2017
@boegel boegel modified the milestones: 3.x, 4.x Feb 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants