Many times, I found this issue, but I never tried to solve it. AFAIK, It's
a common situation on Windows.

My research:
http://stackoverflow.com/questions/8465248/node-js-what-is-node-waf-and-how-to-get-it-on-windows


https://github.com/joyent/node/issues/2671

*Stack Overflow*
says<http://stackoverflow.com/questions/8465248/node-js-what-is-node-waf-and-how-to-get-it-on-windows>
that
there is no waf for Windows.

The authors of these modules are encouraged to statically precompile their
native addons for various supported platforms and architectures, rather
than depend on their users to do the compilation on install time. There is
a recent tool (node-bindings <https://github.com/TooTallNate/node-bindings/>)
to help authors in binding their precompiled binaries to JavaScript.

Of course, if the build system of some binary is waf-based originally, then
its portability to Windows seems questionable; at the very least,
it would require some work of modules' authors.


http://blog.nodejs.org/2012/01/23/node-v0-7-1/
where Isaac Schlueter says:

2012/01/26 at 8:05 am
Node-waf doesn’t work on Windows.
We’re working on a solution that will make it easier to get a build
toolchain in Windows based on node-gyp. Many packages will have to be
updated to use this instead, so we’re trying to make it as easy a
transition as possible.
Stay tuned. This will almost certainly be in 0.8.



The basic idea is: package authors should avoid client compilation, and
resort to precompiled stuff using the new tools.

But I don't know how to fix your issue, now. Any suggestions? (Detailed)
steps to compile the offending package on Windows?

On Fri, Mar 9, 2012 at 9:38 AM, Maiah Macariola <[email protected]>
wrote:
>
> Hello,
>
> 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:
>
> D:\tools\workspace-node\hello-node-backbone>npm install restify
> npm http GET https://registry.npmjs.org/restify
> npm http 304 https://registry.npmjs.org/restify
> npm http GET https://registry.npmjs.org/dtrace-provider/0.0.6
> npm http GET https://registry.npmjs.org/http-signature/0.9.8
> npm http GET https://registry.npmjs.org/lru-cache/1.0.5
> npm http GET https://registry.npmjs.org/mime/1.2.5
> npm http GET https://registry.npmjs.org/bunyan/0.6.8
> npm http GET https://registry.npmjs.org/qs/0.4.2
> npm http GET https://registry.npmjs.org/retry/0.6.0
> npm http GET https://registry.npmjs.org/formidable/1.0.9
> npm http GET https://registry.npmjs.org/node-uuid/1.3.3
> npm http GET https://registry.npmjs.org/semver/1.0.13
> npm http GET https://registry.npmjs.org/async/0.1.18
> npm http 304 https://registry.npmjs.org/lru-cache/1.0.5
> npm http 304 https://registry.npmjs.org/bunyan/0.6.8
> npm http 304 https://registry.npmjs.org/dtrace-provider/0.0.6
> npm http 304 https://registry.npmjs.org/http-signature/0.9.8
> npm http 304 https://registry.npmjs.org/mime/1.2.5
> npm http 304 https://registry.npmjs.org/qs/0.4.2
> npm http 304 https://registry.npmjs.org/retry/0.6.0
> npm http 304 https://registry.npmjs.org/formidable/1.0.9
> npm http 304 https://registry.npmjs.org/node-uuid/1.3.3
> npm http 304 https://registry.npmjs.org/semver/1.0.13
> npm http 304 https://registry.npmjs.org/async/0.1.18
> npm http GET https://registry.npmjs.org/asn1/0.1.9
> npm http GET https://registry.npmjs.org/ctype/0.3.1
> npm http GET https://registry.npmjs.org/sprintf/0.1.1
> npm http 304 https://registry.npmjs.org/asn1/0.1.9
> npm http 304 https://registry.npmjs.org/sprintf/0.1.1
> npm http GET https://registry.npmjs.org/sprintf/-/sprintf-0.1.1.tgz
> npm http GET https://registry.npmjs.org/asn1/-/asn1-0.1.9.tgz
> npm http 304 https://registry.npmjs.org/ctype/0.3.1
>
> > [email protected] install
D:\tools\workspace-node\hello-node-backbone\node_modules\restify\node_modules\dtrace-provider
> > node-waf configure build
>
> npm http GET https://registry.npmjs.org/ctype/-/ctype-0.3.1.tgz
> 'node-waf' is not recognized as an internal or external command,
> operable program or batch file.
> npm ERR! error installing [email protected]
> npm ERR! error installing [email protected]
> npm ERR! error rolling back [email protected] Error: UNKNOWN, unknown error
'D:\tools\workspace-node\hello-node-backbone\node_modules\restify\node_modules\___formidable.npm\package\test'
>
> npm ERR! [email protected] install: `node-waf configure build`
> npm ERR! `cmd "/c" "node-waf configure build"` failed with 1
> npm ERR!
> npm ERR! Failed at the [email protected] install script.
> npm ERR! This is most likely a problem with the dtrace-provider package,
> npm ERR! not with npm itself.
> npm ERR! Tell the author that this fails on your system:
> npm ERR!     node-waf configure build
> npm ERR! You can get their info via:
> npm ERR!     npm owner ls dtrace-provider
> npm ERR! There is likely additional logging output above.
> npm ERR!
> npm ERR! System Windows_NT 5.1.2600
> npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program
Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "restify"
> npm ERR! cwd D:\tools\workspace-node\hello-node-backbone
> npm ERR! node -v v0.6.12
> npm ERR! npm -v 1.1.4
> npm ERR! code ELIFECYCLE
> npm ERR! message [email protected] install: `node-waf configure build`
> npm ERR! message `cmd "/c" "node-waf configure build"` failed with 1
> npm ERR! errno {}
> npm ERR!
> npm ERR! Additional logging details can be found in:
> npm ERR!     D:\tools\workspace-node\hello-node-backbone\npm-debug.log
> npm not ok
>
>
> 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.
>
> Any help would be very much appreciated.
>
> Thanks!
> Maiah
>
> --
> 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

-- 
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

Reply via email to