13:08 < hacsheng_> I have a problem with building the mlpack Python bindings. I can use mlpack on CLI. When I open python and import mlpack, it shows no mlpack module.

13:08 < hacsheng_> I use mac (10.11.6)

13:09 < hacsheng_> I use .sh file to install mlpack

13:09 < hacsheng_> this is my .sh below

13:09 < hacsheng_> brew install armadillo #cd .. curl -O http://netcologne.dl.sourceforge.net/project/boost/boost/1.60.0/boost_1_60_0.tar.gz tar zxvf boost_1_60_0.tar.gz cd boost_1_60_0 sh bootstrap.sh ./b2 ./b2 install cd .. git clone https://github.com/mlpack/mlpack cd mlpack mkdir build cd build #cmake .. cmake -D DEBUG=ON -D PROFILE=ON -D BUILD_CLI_EXECUTABLES=ON -D BUILD_PYTHON_BINDINGS=ON ../ make make install

13:10 < hacsheng_> Does anyone encounter this problem before?

13:16 < rcurtin> are the Python bindings available on your PYTHONPATH?

13:16 < rcurtin> I would imagine they installed into /usr/local/lib/python.../ (or somewhere like this)

13:42 < hacsheng_> I thought if I set "BUILD_PYTHON_BINDINGS=ON" before I make, Python bindings will be available...

13:45 < rcurtin> yes

13:45 < rcurtin> and if you build and install the Python bindings

13:45 < rcurtin> you need to ensure that your PYTHONPATH includes the directory they were installed to

13:46 < rcurtin> the first check would be to find the directory that the Python bindings installed to; you could search for mlpack/__init__.py somewhere on your system

14:29 < daivik> rcurtin: Upgrading to boost 1.62 solved the problem. You were right, it was a version issue.

14:30 < rcurtin> daivik: ok, that is good to know

14:31 < daivik> also with v1.58, I can see 3 tests failing when i run mlpack_test -- and all are related to serialization

14:31 < rcurtin> hmm, ok

14:31 < rcurtin> so, if you are feeling up to it, you can test if this patch helps on boost 1.58:

14:31 < rcurtin> https://github.com/mlpack/mlpack/pull/1229

14:31 < rcurtin> unfortunately I can't dig in too deep, because the system with which I'd test boost 1.58 is about to go down for the weekend...

14:32 < rcurtin> but anyway, the serialization issues I mentioned yesterday might be affecting some of those tests... but I am not sure. I'm kind of doubtful it will help your exact case

14:32 < rcurtin> in any case, if you want to keep digging feel free; if not, definitely we should open a github issue at this point so that we can continue to track down the issue

14:34 < daivik> Sure, I've got two docker containers set up now -- one with each boost version. I'll give it a go.

14:36 < rcurtin> thanks, I'll be interested to see what you find

14:36 < rcurtin> boost serialization is really nice but when something goes wrong it's a disaster ...

16:19 < rcurtin> ok, hopefully jenkins-mlpack will come back someday... :)

19:08 < hacsheng> question again: c++ -bundle -undefined dynamic_lookup -arch i386 -arch x86_64 -Wl,-F. build/temp.macosx-10.11-intel-2.7/Users/shengsu/Downloads/c++mlpack/mlpack/build/src/mlpack/bindings/python/mlpack/kmeans.o -L/Users/shengsu/Downloads/c++mlpack/mlpack/build/lib/ -lmlpack -lboost_serialization -o build/lib.macosx-10.11-intel-2.7/mlpack/kmeans.so NOTFOUND clang: error: no such file or directory: 'NOTFOUND' error: command 'c++' faile

19:09 < hacsheng> Is it possible for compiler problem?

19:10 < hacsheng> I use mac (clang)

19:26 < rcurtin> huh, looks like one of the libraries was not found...

19:26 < rcurtin> can you tell me the output of 'grep NOTFOUND CMakeCache.txt'

19:27 < hacsheng> Boost_DIR:PATH=Boost_DIR-NOTFOUND CMAKE_OBJCOPY:FILEPATH=CMAKE_OBJCOPY-NOTFOUND DOXYGEN_DOT_EXECUTABLE:FILEPATH=DOXYGEN_DOT_EXECUTABLE-NOTFOUND DOXYGEN_EXECUTABLE:FILEPATH=DOXYGEN_EXECUTABLE-NOTFOUND OpenMP_CXX_FLAGS:STRING=NOTFOUND OpenMP_CXX_LIB_NAMES:STRING=NOTFOUND OpenMP_C_FLAGS:STRING=NOTFOUND OpenMP_C_LIB_NAMES:STRING=NOTFOUND PKG_CONFIG_EXECUTABLE:FILEPATH=PKG_CONFIG_EXECUTABLE-NOTFOUND TXT2MAN:FILEPATH=TXT2MAN-NOTFOUND

19:34 < rcurtin> ok, so it looks like boost was not found...

19:34 < rcurtin> what was the CMake output?

19:35 < rcurtin> ah, sorry, I think maybe I am incorrect, I think maybe OpenMP wasn't found

19:35 < rcurtin> what is the compiler version?

19:39 < hacsheng> Apple LLVM version 8.0.0 (clang-800.0.42.1)

19:49 < hacsheng> It did work and install successfully 12 hours ago... I try again

19:54 < rcurtin> I thought about it, that version of the compiler has OpenMP support

19:54 < rcurtin> so I am not quite sure what is happening

19:54 < rcurtin> you could remove the full build directory and try again, that may be the right way to go