Databases
StackOverflow2013
Postsdbo
POnowjs/node-proxy fails to install on ubuntu 11.10
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POnowjs/node-proxy fails to install on ubuntu 11.10
    primarykey
    data
    text
    <p>I'm trying to install now.js on ubuntu 11.10 (running on windows with wubi, if that matters). I've downloaded and installed node, npm, and socket.io just fine, but <code>sudo npm install now</code> fails for some reason. I've tried with and without sudo, tried installing it globally, same error. Make is installed just fine...is it some problem with the node-proxy package? For what it's worth, trying <code>npm install node-proxy</code> produces a similar error.</p> <p>node version 0.6.2<br> npm version 1.0.106<br> ubuntu 11.10 (windows with wubi)</p> <p>The log reads, when I try to install now:</p> <pre><code>npm WARN node-proxy@0.5.2 package.json: bugs['web'] should probably be bugs['url'] > node-proxy@0.5.2 install /home/my_name/node_modules/now/node_modules/node-proxy > make BUILDING: C++ Component /bin/sh: node-waf: not found cp: cannot stat `src/build/*/node-proxy.node': No such file or directory make: *** [all] Error 1 npm ERR! error installing node-proxy@0.5.2 Error: node-proxy@0.5.2 install: `make` npm ERR! error installing node-proxy@0.5.2 `sh "-c" "make"` failed with 2 npm ERR! error installing node-proxy@0.5.2 at ChildProcess. (/usr/lib/node_modules/npm/lib/utils/exec.js:49:20) npm ERR! error installing node-proxy@0.5.2 at ChildProcess.emit (events.js:70:17) npm ERR! error installing node-proxy@0.5.2 at maybeExit (child_process.js:359:16) npm ERR! error installing node-proxy@0.5.2 at Process.onexit (child_process.js:395:5) npm ERR! error installing now@0.7.6 Error: node-proxy@0.5.2 install: `make` npm ERR! error installing now@0.7.6 `sh "-c" "make"` failed with 2 npm ERR! error installing now@0.7.6 at ChildProcess. (/usr/lib/node_modules/npm/lib/utils/exec.js:49:20) npm ERR! error installing now@0.7.6 at ChildProcess.emit (events.js:70:17) npm ERR! error installing now@0.7.6 at maybeExit (child_process.js:359:16) npm ERR! error installing now@0.7.6 at Process.onexit (child_process.js:395:5) npm ERR! node-proxy@0.5.2 install: `make` npm ERR! `sh "-c" "make"` failed with 2 npm ERR! npm ERR! Failed at the node-proxy@0.5.2 install script. npm ERR! This is most likely a problem with the node-proxy package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! make npm ERR! You can get their info via: npm ERR! npm owner ls node-proxy npm ERR! There is likely additional logging output above. npm ERR! npm ERR! System Linux 3.0.0-13-generic npm ERR! command "node" "/usr/bin/npm" "install" "now" npm ERR! cwd /home/my_name npm ERR! node -v v0.6.2 npm ERR! npm -v 1.0.106 npm ERR! code ELIFECYCLE npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /home/my_name/npm-debug.log npm not ok</code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJonas
    1. USNoah Gilmore
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POnowjs/node-proxy fails to install on ubuntu 11.10
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload