-
Notifications
You must be signed in to change notification settings - Fork 80
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
Error building Python bindings with boost-python 1.56 #87
Comments
This cannot be reproduced on Ubuntu with boost_python 1.56, so it may very much be OSX specific, and maybe related to macports not providing a proper x86_64 build. Will continue investigations. |
This appears to be a problem with macport not providing a build of boost for gcc, affecting only some versions of OSX. The problem with clang #19 is now fixed, and libcmaes should compile fine without the need for gcc, thus avoiding this problem. Will wait til next release for closing this one though. |
regarding the doc, python part, at https://github.com/beniz/libcmaes/wiki/Building-libcmaes-on-Mac-OSX: I believe it assumes that python is/was installed via mac ports (while installing mac ports is the first point to do). I linked the python I am using
and it seemed to work fine as well. I assume we need to have
(hopefully for the currently active python installation). I still can only use the lib then by calling |
Yes you're right. I am still trying to get it to work with OSX's python (i.e. without the macports one), but boost-python, which bridges C++ with python seems to rely on the macport version. Still investigating (compilation is fine, with /usr/bin/python isn't). |
maybe something like this can help:
|
I believe I don't even have macports python installed (and I definitely deinstalled port's py-numpy), so for me it does work with anaconda python. EDIT: I think I was wrong, it is still the Python from Macports, even though it gives an "Anaconda is brought to you by..." message on startup for some reason. |
OK great! I will report on whether I succeed with the original python version from OSX. |
I am not successful with OSX Python, but I believe this would be another ticket. Closing this due to the fix with clang that makes the boost issue obsolete. But can reopen if it occurs again. My leading hypothesis still being a missing gcc-compiled boost version in last macports. |
The following error has been observed on OS X, more tests required to reproduce and fix:
The text was updated successfully, but these errors were encountered: