Open DarekLin opened 9 years ago
I have the same problem on RPi B+.
The install script works without error. I was using the latest build as of today. Then when I do
./server.js -l 0.0.0.0 -a : -w ~ which is supposed to set the working directory as /home/pi , and then I try to open this
Starting standalone
Warning: running Cloud9 without using HTTP authentication.
Run using --listen localhost instead to only expose Cloud9 to localhost,
or use -a username:password to setup HTTP authentication
Connect server listening at http://10.95.145.56:8181
CDN: version standalone initialized /home/pi/c9sdk/build
Started '/home/pi/c9sdk/configs/standalone' with config 'standalone'!
{ [Error: Cannot find module '/root/.c9/node_modules/pty.js'] code: 'MODULE_NOT_FOUND' } '/root/.c9/node_modules/pty.js'
{ [Error: Cannot find module 'pty.js'] code: 'MODULE_NOT_FOUND' } 'pty.js'
{ [Error: Cannot find module 'pty.nw.js'] code: 'MODULE_NOT_FOUND' } 'pty.nw.js'
unable to initialize pty.js:
PTY is not supported.
PTY is not supported.
PTY is not supported.
PTY is not supported.
PTY is not supported.
This message didnt used to come before, its new. Also, sometimes, I get some install screen on my chrome on my connected machine, which asks to install c9, I dont know where, and then I get the message like DarekLin posted above inside the install box.
Also, pty alone does install in RPi, I tried a simple npm install pty and it installed cleanly. I dont know know though, how I can resolve this issue.
try running
C9_DIR=$HOME/.c9
PATH="$C9_DIR/node/bin/:$C9_DIR/node_modules/.bin:$PATH"
cd $C9_DIR
npm install pty.js
or if the above doesn't work
npm install pty.js --unsafe-perm
Also note if you have a new version of node installed (0.10.28-0.12) deleting ~/.c9 and running https://github.com/c9/install/blob/master/link.sh#L35 can save some space on RPi
I have not tried your workaround, but I did something of my own. I went into /root, which required sudo -i and and then I copied the pty.js folder from one of the successful installs of npm install pty and copied it to the node_modules folder in /root/.c9/, and then the install process on my host machine (what is that btw, and why is it needed ? ) took around 2 hours and gave everything successfully installed and now I am able to run everything, * only if I run the server with a sudo, if I run it without sudo, it again gives a pty not supported message. * Aslo, this leads to the "root" user in my connected machine.
So I think what you suggested might be more permanent.
On further testing, I found a teeny-tiny problem, \ the debugger doesnt stop on breakpoints **. I am running in debug mode. The green bug on the bottom panel is lit. I am placing the breakpoints. I also added few variables to the watch list and couldnt see them as well. Would open a new issue, just want to make sure they are not connected. Another smaller, ignorable issue, is the button, "Preview", it errors on both options.
Posting my output, I only see a few errors at the end there.
Starting standalone
Warning: running Cloud9 without using HTTP authentication.
Run using --listen localhost instead to only expose Cloud9 to localhost,
or use -a username:password to setup HTTP authentication
Connect server listening at http://10.95.145.56:8181
CDN: version standalone initialized /home/pi/c9sdk/build
Started '/home/pi/c9sdk/configs/standalone' with config 'standalone'!
cache /home/pi/c9sdk/build/standalone/skin/default/dark.css
cache hit /home/pi/c9sdk/build/standalone/skin/default/dark.css
1561: Error: ENOENT, stat '/root/.c9/plugins/'
1561: Error: ENOENT, stat '/root/.c9/managed/plugins/'
1561: Error: ENOENT, stat '/root/.c9/dev/plugins/'
Debugger not working seems unrelated. Which runner do you use?
Hey,
Sorry about that, couldnt update the status before, the debugger works well, perfectly.
This worked for me:
~/.c9/node/bin/npm config set unsafe-perm true
@NoobTW : I think your solution requires root access too and it works for pty.js
In case this has not been resolved. Follow the commands below.
sudo apt-get update && sudo apt-get upgrade
wget http://nodejs.org/dist/v0.10.28/node-v0.10.28-linux-arm-pi.tar.gz
cd /usr/local
tar -xzf ~/node-v0.10.28-linux-arm-pi.tar.gz —-strip=1
export NODE_PATH=”/usr/local/lib/node_modules”
node --version
git clone git://github.com/c9/core.git c9sdk
cd c9sdk
scripts/install-sdk.sh
node server.js
./server.js -l 0.0.0.0 -a :
This is all explained in greater detail here:
https://medium.com/@chintanp/using-cloud9-3-0-ide-on-raspberry-pi-954cf2d6ab8e#.dmdtdhxyz
Hmmm... I get this pty.js
error if I run under sudo
but not if I run without sudo
.
Hello, I'm trying to install cloud9 v3 to my raspi2 node -v v0.12.7 and I meet some problem related to:
747 info install pty.js@0.2.8 748 verbose unsafe-perm in lifecycle false 749 info pty.js@0.2.8 Failed to exec install script 750 info /root/.c9/node_modules/pty.js unbuild 751 info preuninstall pty.js@0.2.8 752 info uninstall pty.js@0.2.8 753 verbose true,/root/.c9/node_modules,/root/.c9/node_modules unbuild pty.js@0.2.8 754 info postuninstall pty.js@0.2.8 755 error pty.js@0.2.8 install:
node-gyp rebuild
755 error Exit status 127 756 error Failed at the pty.js@0.2.8 install script. 756 error This is most likely a problem with the pty.js package,node -v v0.12.7