building python bindings with Anaconda (and homebrew / OSX as well) #111
Comments
|
Thanks. Looking into it. |
|
silver6:Axa kegl$ brew --config |
|
I need what says in order to see what python brew is relying on, plus the output of the |
|
|
the output of brew config is in the previous comment |
|
OK, configure should say something about python and it does not, so let's fix this first: then relaunch the EDIT: can you post the full ./configure line ? |
|
Forgot to switch on python. |
|
Looks better, now I'd try: may take a while. |
|
OK Maybe it's boost tht uses the wrong python? mbp-kuomo:gflags-2.0 kegl$ brew reinstall boost --with-python |
|
I know nothing about homebrew but if homebrew says that it is using (from the brew --config) then boost-python should be using the right one as well. |
|
Can you post the compile output when it comes to lcmaes.so please ? to get it, do I can use this trace to better understand what is going on. |
|
|
Looks similar, but I don't understand it |
|
I think a proper solution would be to add cma to homebrew (eventually). |
|
what does 'brew doctor' says ? |
|
Also, could you locate your 'libboost_python.so' file ? In parallel could you send me your 'config.log' file by email please ? One possibility I want to check is whether the build is using the correct boost-python lib. Thanks. |
|
thanks, nothing bad from what I see. |
|
I don't have a libboost_python |
|
even in |
|
mbp-kuomo:Applications kegl$ cd /Users/kegl/anaconda/lib |
|
To console you: I can't get hyperopt working either :) |
can you paste the error if it is short enough, as it may shed light on the configuration problem. The whole thing appears to be a conflict between python-apple and python from homebrew. |
|
Also, do you have ? |
|
It seems different. I can get hyperopt working but not their notebook. |
|
/usr/local/binpython: No such file or directory |
|
No /usr/local/bin/python either :) |
|
|
|
no /bin/python either |
|
I see that your configure line is rather minimal, could you try configuring with and/or tell me what says... |
beniz
changed the title
|
OK, so I've successfully compiled both stable and dev versions of libcmaes on OSX with system Python. I do now consider this is a difficulty with Anaconda, and have renamed the ticket accordingly. I am investigating the Anaconda support now, starting with Ubuntu, and later with OSX. |
|
OK, so anaconda works without problem with libcmaes and python bindings on Ubuntu. --> rant begin here: And still trying to come up with a full begin to end solution for OSX of course. EDIT: cleanliness |
|
Got it to work through a complicated process, will post the full doc this afternoon, and if there's a good soul who is willing to replicate, I guess life would be perfect (again) :) |
Compile with Anaconda on UbuntuAssuming anaconda is installed in the following steps should allow you to compile libcmaes and python bindings for anaconda and gcc (anaconda supplies a link to clang, which would otherwise be picked up by libcmaes, it is simpler with gcc). From within |
Compile with Anaconda on OSXAssuming that anaconda is installed in the following steps should allow you to compile libcmaes with python bindings for anaconda:
TIP: if you have already compiled libcmaes, after the call to |
|
This looks promising. When calling I got many of these kind of messages: and finally Is this all right? Then, I get from Looks familiar, I have done |
appears to go through |
|
The early errors in the building libboost look like a gcc / clang mismatch, and since you are using port, I will very probably need to investigate. As for the latter question, you should add to your EDIT: hey, thanks for trying it out so quickly! |
|
FTR, fails with |
|
The output from your configure script would help here. It might be benign. On February 3, 2015 5:00:08 PM GMT+01:00, nikohansen notifications@github.com wrote:
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
The output of |
|
Please do and run the The build of boost looks suspicious but would be a different problem that I can look at from an OSX machine directly. EDIT: clarity |
|
OK, now I see |
|
is |
|
No. |
|
OK, the boost build did fail. the One culprit could that gcc was installed through port and is somehow in the way here. One way to make sure could be to remove all gcc with port and try the boost build anew. I'd understand if you don't want to do this, if only because it remains a hypothesis. |
|
OK, I managed to which might be a trivial problem? |
|
yes! try which after straight compilation should be and elsewhere if you did |
|
Works like charm! :-) Can import |
|
oh great! The boost-python situation is still blurry to me though, did you recompile it or something ? |
|
ah, yes, I did So, I guess, I prevent that EDIT: also |
|
yes, easier I reckon! I'm not sure how often you guys reinstall anaconda, but I could do a script that does the whole set of things above. Just let me know. Waiting to hear from @kegl and I'll close it here. |
|
I've added the instructions for building the Python bindings with Anaconda to https://github.com/beniz/libcmaes/wiki/Python-bindings and https://github.com/beniz/libcmaes/wiki/Building-libcmaes-on-Mac-OSX I am closing this issue until new difficulties arise. |
These install with brew:
autoconf
automake
eigen
libtool
boost has to be installed with
and gflag as to be installed manually
Then we need
and
add
"$HOME/Research/CMAES/libcmaes/python/"
to PYTHONPATH
Then
anaconda python gets stuck with
The text was updated successfully, but these errors were encountered: