Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installed successfully but require 'nn' failed? #85

Closed
wangg12 opened this issue Mar 22, 2016 · 3 comments
Closed

Installed successfully but require 'nn' failed? #85

wangg12 opened this issue Mar 22, 2016 · 3 comments

Comments

@wangg12
Copy link

wangg12 commented Mar 22, 2016

I cloned this repo and built with install.sh. Then I typed require 'nn' in th shell, but got the following error:

/net/wanggu/torch/install/share/lua/5.1/trepl/init.lua:384: /net/wanggu/torch/install/share/lua/5.1/trepl/init.lua:384: /home/wanggu/.luarocks/share/lua/5.1/nn/test.lua:12: attempt to call field 'TestSuite' (a nil value)
stack traceback:
        [C]: in function 'error'
        /net/wanggu/torch/install/share/lua/5.1/trepl/init.lua:384: in function 'require'
        [string "_RESULT={require 'nn'}"]:1: in main chunk
        [C]: in function 'xpcall'
        /net/wanggu/torch/install/share/lua/5.1/trepl/init.lua:651: in function 'repl'
        ...nggu/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:199: in main chunk
        [C]: at 0x00406670

My system is Ubuntu 14.04. My cuda version is 7.5 and my cudnn version is v4-prod.

Anyone can give me a hand?

@wangg12 wangg12 changed the title Installed successful but require 'nn' failed? Installed successfully but require 'nn' failed? Mar 22, 2016
@soumith
Copy link
Member

soumith commented Mar 22, 2016

Do

luarocks install torch

See if that fixes things

@wangg12
Copy link
Author

wangg12 commented Mar 22, 2016

@soumith luarocks install torch is ok, but the error still exists.

@wangg12
Copy link
Author

wangg12 commented Mar 22, 2016

I tried clean.sh update.sh and reinstall. And I removed some packages in ·.local·. Then somehow it was solved. Maybe it is related to confusion between the local packages and the packages in where torch is installed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants