Giter Club home page Giter Club logo

Comments (10)

jarrettgilliam avatar jarrettgilliam commented on May 30, 2024

What commands did you run to produce this error? Also, where is node installed on your system?

from wetty.

russellanam avatar russellanam commented on May 30, 2024

Hi, I have the same problem. I get the exact same error when I run the command "npm install". Get the same error when I try "sudo node-gyp rebuild".

`0: no version information available (required by nodejs)
gyp: Call to 'node -e "require('nan')"' returned exit status 1. while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (/usr/share/node-gyp/lib/configure.js:431:16)
gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:797:12)
gyp ERR! System Linux 3.13.0-36-generic
gyp ERR! command "nodejs" "/usr/bin/node-gyp" "rebuild"
gyp ERR! cwd /tmp/wetty/wetty/node_modules/pty.js
gyp ERR! node -v v0.10.25
gyp ERR! node-gyp -v v0.10.10
gyp ERR! not ok
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR! weird error 1
npm ERR! not ok code 0`

from wetty.

russellanam avatar russellanam commented on May 30, 2024

Hi,
I am using the latest version of Node according to apt-get and it seems to be v.3.2-7.4. However when I type 'node -v' it shows blank.
Thanks
-M A

Date: Wed, 10 Feb 2016 12:40:22 -0800
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: [wetty] Installing Failed Pty.js (#43)

I see this warning here:

npm WARN This failure might be due to the use of legacy binary "node"

What version of node are you running? (node -v)


Reply to this email directly or view it on GitHub.

from wetty.

jarrettgilliam avatar jarrettgilliam commented on May 30, 2024

That's strange. You might need a compatibility symbolic link.

From nodejs.org:

A Node.js package is also available in the official repo for Debian Sid (unstable), Jessie (testing) and Wheezy (wheezy-backports) as "nodejs". It only installs a nodejs binary, so you might want to ln -s /usr/bin/nodejs /usr/bin/node for many things to work.

How did you install nodejs on your system? Did you install the default package from your package manager or download one directly from https://nodejs.org/?

from wetty.

russellanam avatar russellanam commented on May 30, 2024

Hi,
I just ran "ln -s /usr/bin/nodejs /usr/bin/node" and 'node -v' still shows blank. I installed node via "apt-get install node". I have tried installing and reinstalling node again and it's still blank. In case it matters, I am doing all these on the default AWS instance and all packages are updated.
Date: Wed, 10 Feb 2016 13:35:47 -0800
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: [wetty] Installing Failed Pty.js (#43)

That's strange. You might need a compatibility symbolic link.

From nodejs.org:

A Node.js package is also available in the official repo for Debian Sid (unstable), Jessie (testing) and Wheezy (wheezy-backports) as "nodejs". It only installs a nodejs binary, so you might want to ln -s /usr/bin/nodejs /usr/bin/node for many things to work.

How did you install nodejs on your system? Did you install the default package from your package manager or download one directly from https://nodejs.org/?


Reply to this email directly or view it on GitHub.

from wetty.

jarrettgilliam avatar jarrettgilliam commented on May 30, 2024

What is the output of the following commands?

ls -l "$(which node)"
ls -l "$(which nodejs)"
nodejs -v

from wetty.

russellanam avatar russellanam commented on May 30, 2024

Hi,
Here is the output:
ubuntu@ip-1-0-1-50:$ ls -l "$(which node)"lrwxrwxrwx 1 root root 9 Oct 29 2012 /usr/sbin/node -> ax25-nodeubuntu@ip-1-0-1-50:$ ls -l "$(which nodejs)"-rwxr-xr-x 1 root root 1462424 Mar 27 2014 /usr/bin/nodejsubuntu@ip-1-0-1-50:~$ nodejs -vnodejs: /usr/local/MATLAB/MATLAB_Compiler_Runtime/v83/bin/glnxa64/libcrypto.so.1.0.0: no version information available (required by nodejs)nodejs: /usr/local/MATLAB/MATLAB_Compiler_Runtime/v83/bin/glnxa64/libssl.so.1.0.0: no version information available (required by nodejs)nodejs: /usr/local/MATLAB/MATLAB_Compiler_Runtime/v83/bin/glnxa64/libssl.so.1.0.0: no version information available (required by nodejs)v0.10.25

Date: Wed, 10 Feb 2016 13:57:13 -0800
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: [wetty] Installing Failed Pty.js (#43)

What is the output of the following commands?

ls -l "$(which node)"

ls -l "$(which nodejs)"

nodejs -v


Reply to this email directly or view it on GitHub.

from wetty.

jarrettgilliam avatar jarrettgilliam commented on May 30, 2024

It looks like you have a couple of options.

  1. You can try installing nodejs-legacy as described here. This is probably your best bet.
  2. If that doesn't work you could try to install a newer version of node.
  3. If none of the above works you could manually create a compatibility symbolic link. In your case specifically this should work:
rm /usr/sbin/node
ln -s /usr/bin/nodejs /usr/sbin/node

Hope that helps,
Jarrett

from wetty.

russellanam avatar russellanam commented on May 30, 2024

Hi Jarrett,
Thank you so much for your help. I am very grateful and the problem has been finally solved. Wetty is running perfectly and works great. Just a quick question, is it possible to login to SSH with wetty using keys instead of user/pass? I mean just typing the username and it gets the SSH authentication key from a pre-specified file?
Thanks a lot again!
-M Anam.

Date: Wed, 10 Feb 2016 15:39:06 -0800
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: [wetty] Installing Failed Pty.js (#43)

It looks like you have a couple of options.

You can try installing nodejs-legacy as described here. This is probably your best bet.

If that doesn't work you could try to install a newer version of node.

If none of the above works you could manually create a compatibility symbolic link. In your case specifically this should work:

rm /usr/sbin/node
ln -s /usr/bin/nodejs /usr/sbin/node

Hope that helps,

Jarrett


Reply to this email directly or view it on GitHub.

from wetty.

jarrettgilliam avatar jarrettgilliam commented on May 30, 2024

Try --sshauth publickey. Closing.

from wetty.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.