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/
< M7Ain7Soph77Ain7> @shrit:matrix.org a page full of errors. For example
< M7Ain7Soph77Ain7> /usr/local/lib/libboost_serialization.a(basic_iarchive.o): duplicate section `.rdata$_ZTIN5boost12noncopyable_11noncopyableE[__ZTIN5boost12noncopyable_11noncopyableE]' has different size
< M7Ain7Soph77Ain7> AND: undefined reference to `mlpack::bindings::cli::PrintHelp(std::string const&)'
< M7Ain7Soph77Ain7> /usr/lib/gcc/i686-pc-cygwin/10/../../../../i686-pc-cygwin/bin/ld: CMakeFiles/mlpack_adaboost.dir/adaboost_main.cpp.o:adaboost_main.cpp:(.text+0x68ce): undefined reference to `mlpack::adaboost::AdaBoostModel::AdaBoostModel()'
< M7Ain7Soph77Ain7> undefined reference to `mlpack::adaboost::AdaBoostModel::Classify(arma::Mat<double> const&, arma::Row<unsigned int>&, arma::Mat<double>&)'
< M7Ain7Soph77Ain7> undefined reference to `mlpack::util::PrefixedOutStream::operator<<(char const*)'
ImQ009 has joined #mlpack
ImQ009 has quit [Quit: Leaving]
ImQ009 has joined #mlpack
ImQ009 has quit [Read error: Connection reset by peer]
ImQ009 has joined #mlpack
ImQ009 has quit [Quit: Leaving]
< shrit[m]> What are the system you are using? It seems that the linker is unable to find any of the file that have just been compiled.
< shrit[m]> * What are the system configurations you are using? It seems that the linker is unable to find any of the file that have just been compiled.
< shrit[m]> Do you have several version of mlpack compiled on your machine?
ImQ009 has joined #mlpack
< M7Ain7Soph77Ain7> @shrit:matrix.org Only one version of mlpack
< M7Ain7Soph77Ain7> and this is for gcc -v
< shrit[m]> I think there is only a path issue in your case, in which the linker is not able to find the compiled mlpack library. However, I have never used Cygwin or Windows, so maybe I am wrong
< shrit[m]> Usually on Linux you have an LD_LIBRARY_PATH that need to be set, or there is a default path for the library but I do not know how this works for Windows
< shrit[m]> * Usually on Linux you have a LD_LIBRARY_PATH that need to be set, or there is a default path for the library but I do not know how this works for Windows
ImQ009 has quit [Quit: Leaving]
< rcurtin[m]> got a Pinebook Pro today... something new to test our arm code on :)
< shrit[m]> Ah Pinebook
< shrit[m]> Ah, it is Pinebook Pro 👍️
< shrit[m]> Is it faster than a Raspberry Pi 4?
< rcurtin[m]> I have no idea, maybe? the specs seem similar to my old Chromebook Plus, maybe a bit faster
< rcurtin[m]> but I was excited about an 'open source laptop', so let's see if I can make it useful :)
< shrit[m]> There is an open source laptop
< shrit[m]> I do not know at what level the Pinebook is opensource. However, MNT reform is completely open, but much more expensive
< rcurtin[m]> yeah, very cool, I will have to look into it
< rcurtin[m]> I think the CPU in the Pinebook is a Rockchip model, but I'm not sure if it's actually 'open hardware'
< shrit[m]> You can find out easily, if it is open hardware it should not need a blob driver for the kernel
< shrit[m]> and therefore, you can install any Linux kernel you want
< shrit[m]> maybe not the schematics, but at least software
< zoq> rcurtin[m]: Nice, I like the design as well.
< zoq> I guess if you like to build mlpack the main question is how much RAM do you have (hopefully that changes soon).
< shrit[m]> Well, the basic question, do you need to build mlpack for arm on arm machine
< shrit[m]> ?
< zoq> I would think so, looking on the recent apple lineup, I think ARM is going to be the platform in the next years.
< shrit[m]> That is true but in that case, you will already have a powerful machine provided by Apple.
< shrit[m]> Also, I do believe that they will switch to RISCV in a couple of years, maybe they moved too late to ARM, we will see
< zoq> I mean it's not only apple, the chromebooks are ARM based as well, I guess most people think about devices like an RPI when they hear ARM.
< shrit[m]> We should not forget in the future one might need to cross compile from ARM to intel when things change
< zoq> hehe, true