You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
as title
if I install gmplabtools with python setup.py install the pamm executable that is put un the directory ../gmplabtools-0.0.0-py3.9.egg/gmplabtools/pamm/bin is a mac executable:
I think the reason why that happens is that you need to run python setup.py compile first, that creates the executable, while in your case, you are probably using the executable found in the repo (which should probably not be there).
To fix this you can try to delete the exec in the .gmplabtools/pamm/bin folder and the compile with the command above.
To make the process clearer and avoid confusion:
delete the exec in the .gmplabtools/pamm/bin folder and add an empty .gitkeep file;
add the "./gmplabtools/pamm/bin/*" folder here as a part of cleanup directories
Ok, I'm creating a pull request to solve the issue.
I think the problem is if you find a user like me that goes for setup.py install without reading first the README.
The idea of shipping a precompiled pamm exec is not a bad idea tough. pamm depends on blas and lapack for compiling. If blas and lapack are not on the system a non sudoer o a non expert user can have a hard time in compiling pamm
as title
if I install gmplabtools with
python setup.py install
thepamm
executable that is put un the directory../gmplabtools-0.0.0-py3.9.egg/gmplabtools/pamm/bin
is a mac executable:The text was updated successfully, but these errors were encountered: