verne.freenode.net changed the topic of #mlpack to: http://www.mlpack.org/ -- We don't respond instantly... but we will respond. Give it a few minutes. Or hours. -- Channel logs: http://www.mlpack.org/irc/
stephentu_ has quit [Ping timeout: 264 seconds]
stephentu_ has joined #mlpack
stephentu_ has quit [Ping timeout: 252 seconds]
vedhu63w has joined #mlpack
stephentu has quit [Ping timeout: 256 seconds]
govg has quit [Ping timeout: 244 seconds]
govg has joined #mlpack
govg has quit [Quit: leaving]
curiousguy13 has joined #mlpack
vedhu63w_ has joined #mlpack
Kallor has joined #mlpack
< Kallor>
Hello, I'm new here
< Kallor>
I'd like to contribute and I have good grasp on algorithms
< Kallor>
But would I need specialized knowledge in machine learning to contribute?
< naywhayare>
Kallor: not necessarily, but it's certainly helpful
< naywhayare>
if you've downloaded mlpack and looked through the tutorials (http://www.mlpack.org/tutorial.html) and have a basic idea of how the library is laid out,
< naywhayare>
most of them are marked with a difficulty, so that might help you figure out some issues that you can handle
vedhu63w_ has quit [Quit: Leaving]
curiousguy13 has quit [Ping timeout: 276 seconds]
curiousguy13 has joined #mlpack
Charly_ has joined #mlpack
< Charly_>
Hi !
< Charly_>
I'm new to mlpack and not really good with Ubuntu and I fail installing it... Someone can help ?
< Charly_>
Can someone help me please ?* (sorry, I'm suite tired, my english is worst each minute passing)
< naywhayare>
hi Charly_, if you are on Ubuntu why not just install it through apt?
< naywhayare>
i.e. apt-get install libmlpack-dev
< Charly_>
I followed instructions from the website
< naywhayare>
an install through apt will be easier
< naywhayare>
but if you want to compile from source I can help
< Charly_>
hmm.. ok, i'll go kill myself for the last 30 minutes and retry ><
< naywhayare>
but I need to know the errors that you encountered
< naywhayare>
no need to kill yourself... :)
< Charly_>
just joking, I'll install it with apt
< Charly_>
but I'm curious
< Charly_>
my error is at cmake step
< naywhayare>
okay
< naywhayare>
can you paste the output?
< Charly_>
The CXX compiler identification is unknown
< Charly_>
the entire message
< Charly_>
"-- The CXX compiler identification is unknown CMake Error: your CXX compiler: "CMAKE_CXX_COMPILER-NOTFOUND" was not found. Please set CMAKE_CXX_COMPILER to a valid compiler path or name. -- Armadillo libraries: /usr/lib/libarmadillo.so CMake Warning at CMakeLists.txt:88 (message): This is a 64-bit system, but Armadillo was compiled without 64-bit index support. Consider recompiling Armadillo with ARMA_64BIT_WORD to enable 64
< naywhayare>
ah, you probably don't have gcc installed
< naywhayare>
or g++ or clang
< Charly_>
certainly
< naywhayare>
you could get that tjroug
< naywhayare>
*you could get that through apt
< Charly_>
it says I already have gcc
< Charly_>
must be with Ubuntu now
< naywhayare>
but you need g++ too
< Charly_>
I test that =)
< Charly_>
my hero \o/
< Charly_>
thanks !
< Charly_>
I work in machine learning with windows for too long I guess ^^'
< naywhayare>
:)
stephentu has joined #mlpack
< stephentu>
naywhayare: that sounds like a lot of fun
govg has joined #mlpack
govg is now known as Guest43057
Guest43057 has quit [Client Quit]
govg_ has joined #mlpack
vedhu63w has quit [Quit: Leaving]
< naywhayare>
stephentu: the weird DNS issues? yeah...
< naywhayare>
it looks like it's some bizarre spanning tree issue -- but I can't say more than that since it's been years since I've debugged networks and also because I'm not the one doing the debugging :)
< naywhayare>
I'm waiting on a new switch to drop in place in hopes that it will resolve the issue
< zoq>
I guess big is down for the same issue?
< naywhayare>
yeah, I tore out all the network cables for testing
< naywhayare>
it's a very odd issue... connections have no problems to systems on the 143.215.129.x and 143.215.131.x subnets
< naywhayare>
but sometimes fails for the 143.215.128.x network (which is what bodyguard, the NFS server, is on)
< zoq>
This random issues are hard to track down and it is even harder if you can't just debug the network by yourself
< naywhayare>
apparently those particular switches are known for overheating, and maybe putting it in the middle of the stack has caused it to fail because of heat or something...
< naywhayare>
maybe life would be a million times easier if we just used EC2 instances