ChanServ changed the topic of #mlpack to: "mlpack: a fast, flexible machine learning library :: We don't always respond instantly, but we will respond; please be patient :: Logs at http://www.mlpack.org/irc/
< rcurtin>
HimanshuPathakGi: awesome! maybe with -DCMAKE_BUILD_TYPE=Release?
< chopper_inbound[>
Hi @lozhnikov:matrix.org, I am really sorry for not joining the yesterday's video-chat because the moment I joined, my headphones : "battery low" :( . If you agree, can we have another video-chat before next week?
< chopper_inbound[>
Also, could you please look into #2398, I had some doubts in backward function
< HimanshuPathakGi>
rcurtin yeah already tried that but mlpack is compiling with release build and configuration of visual studio remains same don't know why I will try to find out.
< rcurtin>
HimanshuPathakGi: hmm, I took a quick look at recipe/bld.bat, maybe there needs to be an option specified to ninja?
< rcurtin>
abernauer[m]: yeah, it should be, I think anyone can just join it at any time
< rcurtin>
(it's password protected now, but the password is just the name of the library, so it should be easy. the password is just to keep bots out primarily)
< abernauer[m]>
Yeah I was able to join the meeting
< zoq>
kartikdutt18Gitt: Sorry haven't checked the latest update on the PR.
< kartikdutt18Gitt>
No worries, just wanted to understand something. Thanks a lot.
< AnjishnuGitter[m>
Hi @zoq , #2321 and #2345 are complete from my side, could you have a look at them, whenever you get some time. Thanks!
ImQ009 has quit [Quit: Leaving]
petris has quit [Ping timeout: 264 seconds]
petris has joined #mlpack
< zoq>
AnjishnuGitter[m: Done :)
dendre has joined #mlpack
petris has quit [Ping timeout: 256 seconds]
petris has joined #mlpack
< PranavReddyP16Gi>
*And I don't know if this is required but Makefile2 line 6654 is : $(MAKE) -f src/mlpack/tests/CMakeFiles/mlpack_test.dir/build.make src/mlpack/tests/CMakeFiles/mlpack_test.dir/build
< rcurtin>
PranavReddyP16Gi: what is the error message from the compiler? you've only posted a line from make that says that there was a compilation failure; what was the actual compilation failure from the compiler?
< rcurtin>
(you should be able to get it if you just scroll up a bit. there is probably a lot of output though... the more you can capture the easier it is to figure out what's going on :))
< HimanshuPathakGi>
rcurtin I think I have solved the problem with boost::program_option linking but now I have to fight with boost::throw_exception I used CMAKE_CXX_FLAGS to solve this but the Debug and Release problem is not yet solved thanks for sharing that link it was quite helpful :)
< rcurtin>
HimanshuPathakGi: awesome! let me take a look at it now and see what's happening
< rcurtin>
I can finally live up to my promise of saying I would look at it; I have a few free minutes :)
< HimanshuPathakGi>
Thanks for the help
< rcurtin>
looks like it's failing to link against lapack and blas though?
< rcurtin>
correct me if I'm wrong, that seems to be the same log---build id 158926
< rcurtin>
in any case, it seems to be the same linker errors:
< rcurtin>
2020-05-08T22:01:54.0676769Z armadillo.lib(wrapper.cpp.obj) : error LNK2019: unresolved external symbol zgehrd_ referenced in function wrapper_zgehrd_
< HimanshuPathakGi>
Yes this error is same in both builds
< HimanshuPathakGi>
I thought I will first sovle all the error for boost library
< HimanshuPathakGi>
error LNK2019: unresolved external symbol "void __cdecl boost::throw_exception(class std::exception const &)" (?throw_exception@boost@@YAXAEBVexception@std@@@Z) referenced in function "int const & __cdecl boost::any_cast<int const &>(class boost::any &)" (??$any_cast@AEBH@boost@@YAAEBHAEAVany@0@@Z)
< HimanshuPathakGi>
This is the one I am talking about
< HimanshuPathakGi>
But the log you shared contains this error error LNK2001: unresolved external symbol "class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > boost::program_options::arg" (?arg@program_options@boost@@3V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@A)
< HimanshuPathakGi>
Which I was previously trying to solve
< rcurtin>
ohh, I see, ok... let me keep reading
< rcurtin>
ok, left some comments... little by little, maybe we are getting closer...
< rcurtin>
I'll try to start paying attention to this again and watching each of the builds