cameron.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/
jbc__ has joined #mlpack
jbc_ has quit [Ping timeout: 255 seconds]
jbc__ is now known as jbc_
tarun_ml_enthusi has joined #mlpack
tarun_ml_enthusi has quit [Quit: Page closed]
george_ has joined #mlpack
< george_> Hello, I have written a fancy n-body simulation that successfully uses mlpack, and began the process of installing it on a supercomputer cluster. Sadly, not all the dependencies were available, so I had to install armadillo and a subset of boost in my home directory. After doing this, mlpack failed to build properly. I suspect I made a subtle mistake in installing, and think it might be obvious from the error messages. If there is any clear
< george_> On running Cmake with -DARMADILLO_INCLUDE_DIR and DARMADILLO_LIBRARY set, i get a message that " (/home/gih/gihLib/armadillo/usr/include; /usr/include/armadillo_bits/config.hpp) does not exist!) "
< george_> however, the file config.hpp is indeed present in the /home/gih/gihLib/armadillo/usr/include, and I am not sure how to parse this message. It seems to indicate that cmake is looking in /usr (which I have no ability to install to)
< george_> boost finds the libraries program_options, unit_test_framework and random (but does not mention math)
< george_> when I run make, I receive a number of errors, each of the form home/gih/gihLib/armadillo/usr/include/armadillo_bits/traits.hpp:614: error: ‘std::__traitor<std::__is_integer<unsigned int>, std::__is_floating<unsigned int> >::<anonymous enum>’ is/uses anonymous type
< george_> If there is anyone who has any idea, or wants to see more output, let me know and I can send an email/more private message
< naywhayare> george_: hello there
< george_> hello
< naywhayare> I'm glad you got your simulation working
< naywhayare> can you show me how you ran CMake?
< george_> yes:
< george_> cmake -DARMADILLO_INCLUDE_DIR=~gih/gihLib/armadillo/usr/include/ -DARMADILLO_LIBRARY=~gih/gihLib/armadillo/usr/lib64/libarmadillo.so -DBOOST_ROOT=/home/gih/boost_compact -DBOOST_LIBRARYDIR=/home/boost_compact/stage/lib ../
< naywhayare> I think what is happening is that for some reason, ARMADILLO_INCLUDE_DIR is set to multiple directories: "/home/gih/gihLib/armadillo/usr/include; /usr/include/armadillo_bits"
< naywhayare> given the output that you gave
< naywhayare> but why this is... that's the tricky part. are you using 1.0.10, trunk, or some other version? (so I know which FindArmadillo.cmake to inspect)
< naywhayare> also, you say that the configuration is successful and you are then able to build?
< george_> here is the output:
< george_> [gih@della3 build]$ cmake -DARMADILLO_INCLUDE_DIR=~gih/gihLib/armadillo/usr/include/ -DARMADILLO_LIBRARY=~gih/gihLib/armadillo/usr/lib64/libarmadillo.so -DBOOST_ROOT=/home/gih/boost_compact -DBOOST_LIBRARYDIR=/home/boost_compact/stage/lib ../
< george_> -- Armadillo HDF5 support is enabled and manual linking is required.
< george_> -- Armadillo libraries: /home/gih/gihLib/armadillo/usr/lib64/libarmadillo.so;/usr/lib64/libhdf5.so;/usr/lib64/libz.so;/usr/lib64/libm.so
< george_> CMake Warning at CMakeLists.txt:74 (message): Armadillo configuration file (/home/gih/gihLib/armadillo/usr/include;/usr/include/armadillo_bits/config.hpp) does not exist!
< george_> -- Boost version: 1.55.0
< george_> -- Found the following Boost libraries:
< george_> -- program_options
< george_> -- unit_test_framework
< george_> -- random
< george_> CMake Warning at CMakeLists.txt:291 (message): txt2man not found; man pages will not be generated.
< george_> -- Configuring done
< george_> -- Generating done
< george_> -- Build files have been written to: /home/gih/thirdPartySoftware/mlpack-1.0.10/build
< george_> I am using mlpack-1.0-10
< george_> and I was able to begin the build process after this
< naywhayare> ok, I see the Armadillo warning message issue and know how to fix that. that's a minor issue which shouldn't affect the build
< naywhayare> I'll fix that for the next release shortly, but you shouldn't need to worry about it. what that part of the CMake configuration is doing is checking whether or not ARMA_64BIT_WORD is enabled on a 64-bit system and issuing an informative warning if not
< naywhayare> so, it's just checking stuff, not actual configuration
< naywhayare> which compiler are you using? (and which version?)