03:49 < metahost> zoq: Got it! Thanks! :) I'll start by looking into the dependency graphs for ensmallen and then move on to the other libraries as well.

08:09 < jenkins-mlpack2> Project docker mlpack nightly build build #596: FAILURE in 2 hr 55 min: http://ci.mlpack.org/job/docker%20mlpack%20nightly%20build/596/

10:56 < Nakul[m]> > Nakul: Let's see if that works.

10:56 < Nakul[m]> It works thanks

13:56 < Nakul[m]> zoq: done your suggested change https://github.com/mlpack/mlpack/pull/2075 , see if this fine :)

21:05 < HimanshuPathakGi> Hey rcurtin I am facing an error on PR https://github.com/conda-forge/mlpack-feedstock/pull/18 Which is D:/bld/mlpack_1580241535418/_h_env/Library/lib/armadillo.lib: error adding symbols: File format not recognized

21:05 < HimanshuPathakGi> collect2.exe: error: ld returned 1 exit status

21:05 < HimanshuPathakGi> I think this is because linker is not able to recognise those can you suggest Can you please suggest What can I do for this

21:10 < rcurtin> HimanshuPathakGi: is MSVC or MinGW being used to compile?

21:10 < rcurtin> also, does the file armadillo.lib exist? or is it, e.g., armadillo.dll.a?

21:11 < HimanshuPathakGi> MSVC is being used

21:13 < HimanshuPathakGi> Hey rcurtin how can I check armadillo.lib exist or not in the build

21:13 < rcurtin> you could just add a `dir` or `ls` to the build commands :)

21:14 < rcurtin> that's how I debug appveyor

21:14 < HimanshuPathakGi> Ok I will try this thanks for helping

21:15 < rcurtin> so, a thing to know is that Armadillo can be configured so that it's header-only and there's no library to link against

21:15 < rcurtin> it turns out, that file libarmadillo.so or libarmadillo.dll or libarmadillo.lib (the extension depends on the platform) is actually just a wrapper around the BLAS and LAPACK libraries

21:16 < rcurtin> so it's possible, if ARMA_USE_WRAPPER is not defined in armadillo_bits/config.hpp, to just link *directly* to the BLAS and LAPACK libraries

21:16 < rcurtin> if this is the configuration of Armadillo that's being used by conda (I'm not sure if it is), then you could perhaps simply omit the Armadillo library path

21:16 < rcurtin> but, listing the files in the lib/ directory should show more of what's going on

21:20 < HimanshuPathakGi> I tried already by omiting armadillo path but same thing happend not able to build in windows

21:22 < HimanshuPathakGi> I think listing the lib directory will be more helpful

21:23 < HimanshuPathakGi> (edited) I think listing the lib directory will be more helpful => I already tried by omiting armadillo path but same thing happend not able to build in windows

23:13 < rcurtin> HimanshuPathakGi: yeah, hopefully that helps. fighting with getting mlpack building on different packaging systems has got to be my least favorite thing to do for mlpack---it's basically always awful

23:13 < rcurtin> (yet somehow I sure do seem to spend most of my time doing it :(...)

23:36 < HimanshuPathakGi> Yes rcurtin everytime when I feel like I got the solution new error arrives and yes armadillo.lib do exist I think problem is somewhere else I will try to diagnose it tomorrow right now 4:59AM here😅😅