Hi Spyros, feel free to edit the wiki and add this as the (Windows) details.
Some comments below.. On Thu, Feb 6, 2014 at 9:30 AM, Spyros Vassilaras <[email protected]> wrote: > > 1) When getting the nupic codebase from GitHub with the command "git > clone https://github.com/numenta/nupic.git"; > > script files were automatically transformed to dos format. The first > symptom of this was to get "command not found" and "unexpected end of file" > errors when running env.sh (and .bashrc). Moreover, this created fatal > errors to the whole build process. Although individual files can be > repaired to unix format by using the utility dos2unix <filename>, it is a > huge task to find and convert all such files in the directory tree. The > solution is to enter the command "git config --global core.autocrlf false" > in the Git Shell before issuing the command "git clone > https://github.com/numenta/nupic.git";. > good point! definitely add this one. Maybe just try without the --global (global adds the option for all git projects, w/o it it should only apply to the current -nupic- project.) > 2) Running the "pip" command requires su privileges "sudo pip ..." > otherwise it ends with a "permission denied" error message. However, if you > run the build.sh with sudo, you are going to build the executables under > /root and end up in a big mess. > Preferable method is to avoid using sudo (=global system changes), running pip with --user flag should do the work w/o it. Also, you don't want to call ./build.sh with sudo (because you've 'source env.sh' as a normal user, so the variables are set for you-the normal user, not root(=sudo)). > 3) Maybe this is obvious to most people but it had me wondering for > sometime from which directory to run each command: the "sudo pip" command > should be ran from within $NUPIC and the "build.sh" from within $HOME. > Actually, I'd believe it's the other way around :) Pip is "python package installer", so it could be called from anywhere (within the same python environment), and './build.sh' (note the '.') should be called from $NUPIC, but with full path (/home/john/nupic/build.sh) it could be called from anywhere (note $NUPIC and $NTA need to be set, did you run 'source env.sh'?) > > Keep up the good work! > > Spyros > Thanks for sharing with us and please add to wiki for others, Cheers, Mark > > -- Marek Otahal :o)
_______________________________________________ nupic mailing list [email protected] http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org
