Hi Austin, I was able to build nupic at last, however some tests are not passing and I'm not sure why (perhaps my set-up). This is what I did:
On a clean Debian 7.7 installation, I followed every step listed in https://github.com/numenta/nupic/wiki/Installing-NuPIC-on-Ubuntu (which says that the build process was tested on Ubuntu 12.04.5 for both *32bit* and *64bit. *Is this doc outdated?) - Updated apt-get - Installed required packages (git, automake, python-dev, ...) - Installed GCC 4.7+ - Installed SWIG - Cloned the nupic repo and set the environment variable $NUPIC to that location - Used pip to install the required Python modules Note that the next step listed there is to build nupic. This is where my previous attempts failed (with the LIB_STATIC_YAML_CPP_LOC undefined), so I downloaded and installed yaml-cpp-0.3 from https://code.google.com/p/yaml-cpp/ and then tried to build nupic.core first following the instructions in https://github.com/numenta/nupic/wiki/NuPIC%27s-Dependency-on-nupic.core (I followed the second method under the User Overrides section) - Cloned the repo from https://github.com/numenta/nupic.core - mkdir -p nupic.core/build/scripts - cd nupic.core/build/scripts - cmake -DLIB_STATIC_YAML_CPP_LOC="/path/to/yaml/installation/.../build/libyaml-cpp.a" ../../src -DCMAKE_INSTALL_PREFIX=../release - make -j4 - make install Everything went well, 0 errors returned. Then I was able to build nupic: - cd $NUPIC - python setup.py install --cmake_options="-DNUPIC_CORE=/path/to/nupic.core/../build/release/ -DSWIG_EXECUTABLE=/path/to/swig/.../swig" --user This time I got a lot of warnings about numpy api being obsolete, but the build finished without errors. Then I tried to build and run the tests, but I didn't copy the results to a log file :(. I remember that: - HTM Networking tests: All green - Unit tests: Some networking test didn't pass, I can't remember which - Integration tests: test failed on network_twonode_test.py on line 134 - Swarming tests: A test failed but I don't know which. The test run was taking so long that I got away from the laptop for a minute and when I came back and read the output on the console, the name of the test that failed was way up beyond the scroll limit. I'm going to check it out in more detail tomorrow. Thanks for your help, anyway! 2014-11-29 18:21 GMT-03:00 Austin Marshall <[email protected]>: > I see you're building on 32-bit linux. The yaml-cpp binaries are not > bundled into the nupic repository since it's not one of the officially > supported platforms (64 bit linux and OS X). I haven't personally tested > it on 32-bit linux after the recent changes to the cmake configuration, but > technically, you could build the externals separately and it should work. > > On Fri, Nov 28, 2014 at 4:28 AM, Hernán Erasmo <[email protected]> wrote: > >> I'm trying to install nupic following the instructions on >> https://github.com/numenta/nupic/wiki/Installing-NuPIC-on-Ubuntu >> I'm running Debian 7.7 on a VirtualBox vm. I know that there is already a >> Vagrant set-up, but I wanted to build nupic on my own vm. I guess that if >> we can't find the solution to this problem then I'll use that. >> >> This is the output of 'uname -a' on the vm I'm working: >> >>Linux desarrollo 3.2.0-4-486 #1 Debian 3.2.63-2+deb7u1 i686 GNU/Linux >> >> The first error I get after running 'python setup.py' is this: >> >> >>hernan@desarrollo:~/desarrollo/nupic$ python setup.py install >> --cmake_options="-DSWIG_EXECUTABLE=/home/hernan/software/swig-3.0.2/swig" >> --user >> >>-- The CXX compiler identification is GNU 4.7.2 >> >>-- Check for working CXX compiler: /usr/bin/c++ >> >>-- Check for working CXX compiler: /usr/bin/c++ -- works >> >>-- Detecting CXX compiler ABI info >> >>-- Detecting CXX compiler ABI info - done >> >>Python 2.7.3 >> >>-- Attempting to fetch nupic.core binaries from >> https://s3-us-west-2.amazonaws.com/artifacts.numenta.org/numenta/nupic.core/nupic_core-34e052d58ae57767ca44b3ff1f8ec785669f65e0-linux32.tar.gz >> and save to >> /home/hernan/desarrollo/nupic/extensions/core/build/release/nupic_core-34e052d58ae57767ca44b3ff1f8ec785669f65e0-linux32.tar.gz... >> >>WARNING: gnome-keyring:: couldn't connect to: >> /home/hernan/.cache/keyring-fpdGC8/pkcs11: No such file or directory >> >>CMake Warning at CMakeLists.txt:220 (message): >> >> Error downloading nupic.core package: 22;"HTTP response code said >> error" >> >> I guess that this isn't a big problem, because I read in >> https://github.com/numenta/nupic/wiki/NuPIC%27s-Dependency-on-nupic.core >> that when this happens the default behaviour is to build from a clone of >> the repo: >> >> >>-- Building nupic.core from local checkout >> /home/hernan/desarrollo/nupic/extensions/core... >> >>Cloning into '/home/hernan/desarrollo/nupic/extensions/core'... >> >>remote: Counting objects: 14579, done. >> >>remote: Total 14579 (delta 0), reused 0 (delta 0) >> >>Receiving objects: 100% (14579/14579), 21.02 MiB | 33 KiB/s, done. >> >>Resolving deltas: 100% (6318/6318), done. >> >>Checking out files: 100% (9963/9963), done. >> >>HEAD is now at 34e052d Merge pull request #240 from >> pradeepto/static-nupic-core >> >>-- Building 'nupic.core' library... >> >>-- The CXX compiler identification is GNU 4.7.2 >> >>-- Check for working CXX compiler: /usr/bin/c++ >> >>-- Check for working CXX compiler: /usr/bin/c++ -- works >> >>-- Detecting CXX compiler ABI info >> >>-- Detecting CXX compiler ABI info - done >> >> But then: >> >> >>CMake Error: The following variables are used in this project, but they >> are set to NOTFOUND. >> >>Please set them or make sure they are set and tested correctly in the >> CMake files: >> >>LIB_STATIC_YAML_CPP_LOC >> >> linked by target "nupic_core_solo" in directory >> /home/hernan/desarrollo/nupic/extensions/core/src >> >>-- Configuring incomplete, errors occurred! >> >>make: *** No rule to make target `install'. Stop. >> >>CMake Error at CMakeLists.txt:283 (message): >> >> Compiling 'nupic.core' library within failed >> >>-- Configuring incomplete, errors occurred! >> >>Unable to generate build scripts! >> >> And that's what I've been fighting against for the last 24 hours. My >> first guess was that it had something to do with yaml, so I've downloaded >> and installed yaml-cpp-0.3.0 package from >> http://code.google.com/p/yaml-cpp/ but I'm still getting the same error >> message. I've also tried to install the latest version of yaml (0.5.1) but >> it gave me another kind of error, since it depends on booster. >> >> I don't think however that I should be installing this dependencies by >> hand. I believe that I'm making some kind of mistake somewhere above in the >> installation process, but I can't figure out what it might be. >> >> Thanks for the help. >> >> Hernán. >> > >
