I see, so it seems that we have to wait until v0.8 is released. So sad for windows nodejs developers.
On Friday, March 9, 2012 8:38:37 PM UTC+8, Maiah Macariola wrote: > Hello, > > </div> > I just installed the new version of node as of this moment (0.6.12) in my > Windows machine. And when I executed "npm install restify" command > I got this error below:</div> > > </div> > > D:\tools\workspace-node\hello-<WBR>node-backbone>npm install restify</div> > npm http GET <a href="https://registry.npmjs.org/restify"; > target="_blank">https://registry.npmjs.org/<WBR>restify</a></div> > npm http 304 <a href="https://registry.npmjs.org/restify"; > target="_blank">https://registry.npmjs.org/<WBR>restify</a></div> > npm http GET <a href="https://registry.npmjs.org/dtrace-provider/0.0.6"; > target="_blank">https://registry.npmjs.org/<WBR>dtrace-provider/0.0.6</a></div> > npm http GET <a href="https://registry.npmjs.org/http-signature/0.9.8"; > target="_blank">https://registry.npmjs.org/<WBR>http-signature/0.9.8</a></div> > npm http GET <a href="https://registry.npmjs.org/lru-cache/1.0.5"; > target="_blank">https://registry.npmjs.org/<WBR>lru-cache/1.0.5</a></div> > npm http GET <a href="https://registry.npmjs.org/mime/1.2.5"; > target="_blank">https://registry.npmjs.org/<WBR>mime/1.2.5</a></div> > npm http GET <a href="https://registry.npmjs.org/bunyan/0.6.8"; > target="_blank">https://registry.npmjs.org/<WBR>bunyan/0.6.8</a></div> > npm http GET <a href="https://registry.npmjs.org/qs/0.4.2"; > target="_blank">https://registry.npmjs.org/qs/<WBR>0.4.2</a></div> > npm http GET <a href="https://registry.npmjs.org/retry/0.6.0"; > target="_blank">https://registry.npmjs.org/<WBR>retry/0.6.0</a></div> > npm http GET <a href="https://registry.npmjs.org/formidable/1.0.9"; > target="_blank">https://registry.npmjs.org/<WBR>formidable/1.0.9</a></div> > npm http GET <a href="https://registry.npmjs.org/node-uuid/1.3.3"; > target="_blank">https://registry.npmjs.org/<WBR>node-uuid/1.3.3</a></div> > npm http GET <a href="https://registry.npmjs.org/semver/1.0.13"; > target="_blank">https://registry.npmjs.org/<WBR>semver/1.0.13</a></div> > npm http GET <a href="https://registry.npmjs.org/async/0.1.18"; > target="_blank">https://registry.npmjs.org/<WBR>async/0.1.18</a></div> > npm http 304 <a href="https://registry.npmjs.org/lru-cache/1.0.5"; > target="_blank">https://registry.npmjs.org/<WBR>lru-cache/1.0.5</a></div> > npm http 304 <a href="https://registry.npmjs.org/bunyan/0.6.8"; > target="_blank">https://registry.npmjs.org/<WBR>bunyan/0.6.8</a></div> > npm http 304 <a href="https://registry.npmjs.org/dtrace-provider/0.0.6"; > target="_blank">https://registry.npmjs.org/<WBR>dtrace-provider/0.0.6</a></div> > npm http 304 <a href="https://registry.npmjs.org/http-signature/0.9.8"; > target="_blank">https://registry.npmjs.org/<WBR>http-signature/0.9.8</a></div> > npm http 304 <a href="https://registry.npmjs.org/mime/1.2.5"; > target="_blank">https://registry.npmjs.org/<WBR>mime/1.2.5</a></div> > npm http 304 <a href="https://registry.npmjs.org/qs/0.4.2"; > target="_blank">https://registry.npmjs.org/qs/<WBR>0.4.2</a></div> > npm http 304 <a href="https://registry.npmjs.org/retry/0.6.0"; > target="_blank">https://registry.npmjs.org/<WBR>retry/0.6.0</a></div> > npm http 304 <a href="https://registry.npmjs.org/formidable/1.0.9"; > target="_blank">https://registry.npmjs.org/<WBR>formidable/1.0.9</a></div> > npm http 304 <a href="https://registry.npmjs.org/node-uuid/1.3.3"; > target="_blank">https://registry.npmjs.org/<WBR>node-uuid/1.3.3</a></div> > npm http 304 <a href="https://registry.npmjs.org/semver/1.0.13"; > target="_blank">https://registry.npmjs.org/<WBR>semver/1.0.13</a></div> > npm http 304 <a href="https://registry.npmjs.org/async/0.1.18"; > target="_blank">https://registry.npmjs.org/<WBR>async/0.1.18</a></div> > npm http GET <a href="https://registry.npmjs.org/asn1/0.1.9"; > target="_blank">https://registry.npmjs.org/<WBR>asn1/0.1.9</a></div> > npm http GET <a href="https://registry.npmjs.org/ctype/0.3.1"; > target="_blank">https://registry.npmjs.org/<WBR>ctype/0.3.1</a></div> > npm http GET <a href="https://registry.npmjs.org/sprintf/0.1.1"; > target="_blank">https://registry.npmjs.org/<WBR>sprintf/0.1.1</a></div> > npm http 304 <a href="https://registry.npmjs.org/asn1/0.1.9"; > target="_blank">https://registry.npmjs.org/<WBR>asn1/0.1.9</a></div> > npm http 304 <a href="https://registry.npmjs.org/sprintf/0.1.1"; > target="_blank">https://registry.npmjs.org/<WBR>sprintf/0.1.1</a></div> > npm http GET <a href="https://registry.npmjs.org/sprintf/-/sprintf-0.1.1.tgz"; > target="_blank">https://registry.npmjs.org/<WBR>sprintf/-/sprintf-0.1.1.tgz</a></div> > npm http GET <a href="https://registry.npmjs.org/asn1/-/asn1-0.1.9.tgz"; > target="_blank">https://registry.npmjs.org/<WBR>asn1/-/asn1-0.1.9.tgz</a></div> > npm http 304 <a href="https://registry.npmjs.org/ctype/0.3.1"; > target="_blank">https://registry.npmjs.org/<WBR>ctype/0.3.1</a></div> > > </div> > > [email protected] install > D:\tools\workspace-node\hello-<WBR>node-backbone\node_modules\<WBR>restify\node_modules\dtrace-<WBR>provider</div> > > node-waf configure build</div> > > </div> > npm http GET <a href="https://registry.npmjs.org/ctype/-/ctype-0.3.1.tgz"; > target="_blank">https://registry.npmjs.org/<WBR>ctype/-/ctype-0.3.1.tgz</a></div> > 'node-waf' is not recognized as an internal or external command,</div> > operable program or batch file.</div> > npm ERR! error installing [email protected]</div> > npm ERR! error installing [email protected]</div> > npm ERR! error rolling back [email protected] Error: UNKNOWN, unknown error > 'D:\tools\workspace-node\<WBR>hello-node-backbone\node_<WBR>modules\restify\node_modules\_<WBR>__formidable.npm\package\test'</div> > > </div> > npm ERR! [email protected] install: `node-waf configure build`</div> > npm ERR! `cmd "/c" "node-waf configure build"` failed > with 1</div> > npm ERR!</div> > npm ERR! Failed at the [email protected] install script.</div> > npm ERR! This is most likely a problem with the dtrace-provider package,</div> > npm ERR! not with npm itself.</div> > npm ERR! Tell the author that this fails on your system:</div> > npm ERR! node-waf configure build</div> > npm ERR! You can get their info via:</div> > npm ERR! npm owner ls dtrace-provider</div> > npm ERR! There is likely additional logging output above.</div> > npm ERR!</div> > npm ERR! System Windows_NT 5.1.2600</div> > npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" > "C:\\Program > Files\\nodejs\\node_modules\\<WBR>npm\\bin\\npm-cli.js" > "install" "restify"</div> > npm ERR! cwd D:\tools\workspace-node\hello-<WBR>node-backbone</div> > npm ERR! node -v v0.6.12</div> > npm ERR! npm -v 1.1.4</div> > npm ERR! code ELIFECYCLE</div> > npm ERR! message [email protected] install: `node-waf configure > build`</div> > npm ERR! message `cmd "/c" "node-waf configure build"` > failed with 1</div> > npm ERR! errno {}</div> > npm ERR!</div> > npm ERR! Additional logging details can be found in:</div> > npm ERR! > D:\tools\workspace-node\hello-<WBR>node-backbone\npm-debug.log</div> > npm not ok</div> > > </div></div> > > </div> > Does anyone know what should I do here or there is a bug in this new release > for windows? Because it seems that it is trying to execute 'node-waf' > as said in the log above but it is not existing that's why it fails.</div> > > </div> > Any help would be very much appreciated.</div> > > </div> > Thanks!</div> > Maiah</div> On Friday, March 9, 2012 8:38:37 PM UTC+8, Maiah Macariola wrote: > Hello, > > </div> > I just installed the new version of node as of this moment (0.6.12) in my > Windows machine. And when I executed "npm install restify" command > I got this error below:</div> > > </div> > > D:\tools\workspace-node\hello-<WBR>node-backbone>npm install restify</div> > npm http GET <a href="https://registry.npmjs.org/restify"; > target="_blank">https://registry.npmjs.org/<WBR>restify</a></div> > npm http 304 <a href="https://registry.npmjs.org/restify"; > target="_blank">https://registry.npmjs.org/<WBR>restify</a></div> > npm http GET <a href="https://registry.npmjs.org/dtrace-provider/0.0.6"; > target="_blank">https://registry.npmjs.org/<WBR>dtrace-provider/0.0.6</a></div> > npm http GET <a href="https://registry.npmjs.org/http-signature/0.9.8"; > target="_blank">https://registry.npmjs.org/<WBR>http-signature/0.9.8</a></div> > npm http GET <a href="https://registry.npmjs.org/lru-cache/1.0.5"; > target="_blank">https://registry.npmjs.org/<WBR>lru-cache/1.0.5</a></div> > npm http GET <a href="https://registry.npmjs.org/mime/1.2.5"; > target="_blank">https://registry.npmjs.org/<WBR>mime/1.2.5</a></div> > npm http GET <a href="https://registry.npmjs.org/bunyan/0.6.8"; > target="_blank">https://registry.npmjs.org/<WBR>bunyan/0.6.8</a></div> > npm http GET <a href="https://registry.npmjs.org/qs/0.4.2"; > target="_blank">https://registry.npmjs.org/qs/<WBR>0.4.2</a></div> > npm http GET <a href="https://registry.npmjs.org/retry/0.6.0"; > target="_blank">https://registry.npmjs.org/<WBR>retry/0.6.0</a></div> > npm http GET <a href="https://registry.npmjs.org/formidable/1.0.9"; > target="_blank">https://registry.npmjs.org/<WBR>formidable/1.0.9</a></div> > npm http GET <a href="https://registry.npmjs.org/node-uuid/1.3.3"; > target="_blank">https://registry.npmjs.org/<WBR>node-uuid/1.3.3</a></div> > npm http GET <a href="https://registry.npmjs.org/semver/1.0.13"; > target="_blank">https://registry.npmjs.org/<WBR>semver/1.0.13</a></div> > npm http GET <a href="https://registry.npmjs.org/async/0.1.18"; > target="_blank">https://registry.npmjs.org/<WBR>async/0.1.18</a></div> > npm http 304 <a href="https://registry.npmjs.org/lru-cache/1.0.5"; > target="_blank">https://registry.npmjs.org/<WBR>lru-cache/1.0.5</a></div> > npm http 304 <a href="https://registry.npmjs.org/bunyan/0.6.8"; > target="_blank">https://registry.npmjs.org/<WBR>bunyan/0.6.8</a></div> > npm http 304 <a href="https://registry.npmjs.org/dtrace-provider/0.0.6"; > target="_blank">https://registry.npmjs.org/<WBR>dtrace-provider/0.0.6</a></div> > npm http 304 <a href="https://registry.npmjs.org/http-signature/0.9.8"; > target="_blank">https://registry.npmjs.org/<WBR>http-signature/0.9.8</a></div> > npm http 304 <a href="https://registry.npmjs.org/mime/1.2.5"; > target="_blank">https://registry.npmjs.org/<WBR>mime/1.2.5</a></div> > npm http 304 <a href="https://registry.npmjs.org/qs/0.4.2"; > target="_blank">https://registry.npmjs.org/qs/<WBR>0.4.2</a></div> > npm http 304 <a href="https://registry.npmjs.org/retry/0.6.0"; > target="_blank">https://registry.npmjs.org/<WBR>retry/0.6.0</a></div> > npm http 304 <a href="https://registry.npmjs.org/formidable/1.0.9"; > target="_blank">https://registry.npmjs.org/<WBR>formidable/1.0.9</a></div> > npm http 304 <a href="https://registry.npmjs.org/node-uuid/1.3.3"; > target="_blank">https://registry.npmjs.org/<WBR>node-uuid/1.3.3</a></div> > npm http 304 <a href="https://registry.npmjs.org/semver/1.0.13"; > target="_blank">https://registry.npmjs.org/<WBR>semver/1.0.13</a></div> > npm http 304 <a href="https://registry.npmjs.org/async/0.1.18"; > target="_blank">https://registry.npmjs.org/<WBR>async/0.1.18</a></div> > npm http GET <a href="https://registry.npmjs.org/asn1/0.1.9"; > target="_blank">https://registry.npmjs.org/<WBR>asn1/0.1.9</a></div> > npm http GET <a href="https://registry.npmjs.org/ctype/0.3.1"; > target="_blank">https://registry.npmjs.org/<WBR>ctype/0.3.1</a></div> > npm http GET <a href="https://registry.npmjs.org/sprintf/0.1.1"; > target="_blank">https://registry.npmjs.org/<WBR>sprintf/0.1.1</a></div> > npm http 304 <a href="https://registry.npmjs.org/asn1/0.1.9"; > target="_blank">https://registry.npmjs.org/<WBR>asn1/0.1.9</a></div> > npm http 304 <a href="https://registry.npmjs.org/sprintf/0.1.1"; > target="_blank">https://registry.npmjs.org/<WBR>sprintf/0.1.1</a></div> > npm http GET <a href="https://registry.npmjs.org/sprintf/-/sprintf-0.1.1.tgz"; > target="_blank">https://registry.npmjs.org/<WBR>sprintf/-/sprintf-0.1.1.tgz</a></div> > npm http GET <a href="https://registry.npmjs.org/asn1/-/asn1-0.1.9.tgz"; > target="_blank">https://registry.npmjs.org/<WBR>asn1/-/asn1-0.1.9.tgz</a></div> > npm http 304 <a href="https://registry.npmjs.org/ctype/0.3.1"; > target="_blank">https://registry.npmjs.org/<WBR>ctype/0.3.1</a></div> > > </div> > > [email protected] install > D:\tools\workspace-node\hello-<WBR>node-backbone\node_modules\<WBR>restify\node_modules\dtrace-<WBR>provider</div> > > node-waf configure build</div> > > </div> > npm http GET <a href="https://registry.npmjs.org/ctype/-/ctype-0.3.1.tgz"; > target="_blank">https://registry.npmjs.org/<WBR>ctype/-/ctype-0.3.1.tgz</a></div> > 'node-waf' is not recognized as an internal or external command,</div> > operable program or batch file.</div> > npm ERR! error installing [email protected]</div> > npm ERR! error installing [email protected]</div> > npm ERR! error rolling back [email protected] Error: UNKNOWN, unknown error > 'D:\tools\workspace-node\<WBR>hello-node-backbone\node_<WBR>modules\restify\node_modules\_<WBR>__formidable.npm\package\test'</div> > > </div> > npm ERR! [email protected] install: `node-waf configure build`</div> > npm ERR! `cmd "/c" "node-waf configure build"` failed > with 1</div> > npm ERR!</div> > npm ERR! Failed at the [email protected] install script.</div> > npm ERR! This is most likely a problem with the dtrace-provider package,</div> > npm ERR! not with npm itself.</div> > npm ERR! Tell the author that this fails on your system:</div> > npm ERR! node-waf configure build</div> > npm ERR! You can get their info via:</div> > npm ERR! npm owner ls dtrace-provider</div> > npm ERR! There is likely additional logging output above.</div> > npm ERR!</div> > npm ERR! System Windows_NT 5.1.2600</div> > npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" > "C:\\Program > Files\\nodejs\\node_modules\\<WBR>npm\\bin\\npm-cli.js" > "install" "restify"</div> > npm ERR! cwd D:\tools\workspace-node\hello-<WBR>node-backbone</div> > npm ERR! node -v v0.6.12</div> > npm ERR! npm -v 1.1.4</div> > npm ERR! code ELIFECYCLE</div> > npm ERR! message [email protected] install: `node-waf configure > build`</div> > npm ERR! message `cmd "/c" "node-waf configure build"` > failed with 1</div> > npm ERR! errno {}</div> > npm ERR!</div> > npm ERR! Additional logging details can be found in:</div> > npm ERR! > D:\tools\workspace-node\hello-<WBR>node-backbone\npm-debug.log</div> > npm not ok</div> > > </div></div> > > </div> > Does anyone know what should I do here or there is a bug in this new release > for windows? Because it seems that it is trying to execute 'node-waf' > as said in the log above but it is not existing that's why it fails.</div> > > </div> > Any help would be very much appreciated.</div> > > </div> > Thanks!</div> > Maiah</div> -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
