05:57 < tham> zoq : I hope so

14:13 < uzipaz> zoq: Hello gents, sry I was away, but I followed the advice given and reinstalled boost with --built-type=complete and tried to build the stable mlpack-2.0.1 but I've run into compilation error again, its doesn't seem to be a linking error this time, take look here, http://pastebin.com/FHfWwZ6M

14:13 < uzipaz> rcurtin:

14:13 < uzipaz> tham:

14:15 < tham> uzipaz : This looks like an old bug

14:16 < tham> If remember correct, the solution is add std:: before isnan and isinf

14:16 < tham> if it still can not compile, add header file <cmath>

14:26 < zoq> uzipaz: It's fixed in the master branch, maybe you can build against the master branch?

14:27 < uzipaz> zoq: sure, ill try that

14:45 < uzipaz> zoq: building against the latest master branch, it gives me the same undefined reference errors at [ 25%] Linking CXX executable ../../../../mlpack_adaboost.exe

14:52 < zoq> uzipaz: that's odd, can you run cmake again with '-D DEBUG=OFF -D PROFILE=OFF'

14:53 < uzipaz> zoq: I used, cmake .. -DBOOST_INCLUDEDIR:PATH="C:\BoostLibrary\include" -DBOOST_LIBRARYDIR:PATH="C:\BoostLibrary\lib" -DDEBUG=OFF -DPROFILE=OFF -G "MSYS Makefiles"

14:55 < zoq> uzipaz: oh, okay, does it work with '-DDEBUG=ON -DPROFILE=ON'? If this dosn't help, I'm kind of lost ... I guess I should replicate your setup

14:55 < uzipaz> zoq: alright, ill try with '-DDEBUG=ON -DPROFILE=ON'

14:58 < zoq> uzipaz: tham pointed out that it could fail if you build boost/mlpack with compiler optimizations turned on, so maybe that's the case, not sure ... let's see

14:59 < tham> zoq : I think it is not optimization turn on, but the libraries build with different options

15:00 < tham> Maybe part of the libraries are build with different arch, like stack overflow mentioned(http://stackoverflow.com/questions/14181351/i-got-duplicate-section-errors-when-compiling-boost-regex-with-size-optimizati)

15:01 < tham> maybe some libs are build with different optimization options?

15:06 < uzipaz> zoq: I tried re-compiling with '-DDEBUG=ON -DPROFILE=ON', and got the same result, undefined reference errors at [ 25%] Linking CXX executable ../../../../mlpack_adaboost.exe

15:08 < zoq> uzipaz: hm, does C:\BoostLibrary\lib contain *.lib files?

15:08 < uzipaz> zoq: yes

15:09 < tham> uzipaz : could you paste the whole error messages on pastebin?

15:09 < zoq> uzipaz: When you build mlpack does it link against the *.dll.a file or the *.lib file?

15:11 < uzipaz> tham: http://pastebin.com/r5e1nXg1

15:12 < uzipaz> zoq: I am not sure, I just specify the lib folder to cmake

15:13 < uzipaz> is it possible to build and use mlpack with Microsoft Visual Studio?

15:15 < tham> uzipaz : it is absolutely possible, because I am using it right now

15:15 < tham> I found this line suspicious--Linking CXX shared library ../../libmlpack.dll

15:16 < tham> line 550

15:17 < tham> If I am correct, when bulding libs or apps, we only need to link to lib, not dll, dll is only require at run time

15:18 < uzipaz> tham: maybe its generating a mlpack runtime dll... I dont know

15:19 < tham> uzipaz : maybe you are right

15:21 < tham> Hi, I cannot find any message about

15:21 < tham> libmlpack.lib, libmlpack.a or libmlpack.dll.a

15:21 < uzipaz> uzipaz: I will try to get MVS installed, then ill need your help with getting mlpack running, thank you

15:21 < tham> maybe the make file do not try to build them at all

15:22 < tham> that is why it cannot find the symbol

15:22 < zoq> uzipaz: Can you post the content of the C:\BoostLibrary\lib folder?

15:24 < uzipaz> zoq: http://pastebin.com/fDGKXfs9

15:25 < zoq> uzipaz: Thanks!

15:29 < zoq> uzipaz: Can you build one last time with verbose=1?

15:40 < uzipaz> zoq: http://pastebin.com/7kmxfUkV

15:40 < zoq> uzipaz: hm, also if you have time left, can you remove 'set(Boost_LIBRARIES "")' line 213 in CMakeLists.txt?

15:44 < uzipaz> zoq: you mean before link_directories(${Boost_LIBRARY_DIRS})?

15:44 < zoq> uzipaz: yes, right

15:46 < zoq> uzipaz: Note, that you probably have to rerun cmake

15:53 < uzipaz> zoq: still the same

15:55 < zoq> uzipaz: okay, I'll see if I can replicate the error in the next days, in the meantime you could use msvs

15:55 < uzipaz> zoq: thanks for the help :)

17:07 < tham> uzipaz : If you have any problem when you try to build mlapck with vc2015, I am happy to help

18:02 < uzipaz> tham: I appreciate the help, I am downloading MSVS right now, its gonna take a while, are there any prereqs I need to take care of? I have built all the dependent libraries with mingw, will that be an issue?

18:04 < tham> uzipaz : yap, as far as I know, the c++ binary of mingw and visual c++, their abi are not compatible

18:04 < tham> if you compile your c++ libs by vc2015, then all of your libraries should compiled with vc2015

18:06 < tham> The rules are a little complicated, you can refer to the issue #613

18:06 < tham> Compile the libs and make them work, maybe is the most notorious part of c++, I never like it

18:07 < tham> there are too many build system out there

18:07 < tham> abi of different compilers, compile option are not compatible

18:08 < tham> module should able to make things better, but it cannot make it in 2017, sad