Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems using node-gyp #227

Closed
wittend opened this issue Mar 28, 2013 · 26 comments

Comments

@wittend
Copy link

@wittend wittend commented Mar 28, 2013

I am currently working on a Win7-64 (Ultimate) machine with the
Microsoft Windows SDK for Windows 7 installed. I consistently have
difficulty installing nodejs modules that interest me. Node-gyp seems
to be the one package that is involved. All superficial indicators
seem to say that nodejs, npm, and node-gyp are installed correctly.

The most obvious odd thing I see is the line:

LINK : fatal error LNK1181: cannot open input file 'C:\Users\wittend.node-gyp\0.10.1\node.lib'

By default, there is no copy of node.lib in
'C:\Users\wittend.node-gyp\0.10.1'. There are copies in three
folders beneath this, in ia32, x64, and Release. I gather there may
be a missing environment variable that determines the correct
subfolder to look in.

But Windows, when faced with a path with two consecutive backslashes, sometimes reads them as a single backslash. So windows looks for node.lib in C:\Users\wittend.node-gyp\0.10.1\node.lib. This happened for me with node-gyp 1.10.0, so I moved a copy of node.lib from the \Release folder up a level in that tree. But the problem came back when node-gyp got updated. I am not at all certain that is the correct version of the library to use. And if there is an unset environment variable, what is it?

A full typical example of the output I get is this:

C:\Users\wittend\AppData\Roaming\npm\node_modules\ftdi>node
"C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin....\node_m
odules\node-gyp\bin\node-gyp.js" rebuild
C:\Program Files (x86)\Microsoft Visual Studio
9.0\VC\include\xlocale(342): warning C4530: C++ exception handler
used, but unwind s
emantics are not enabled. Specify /EHsc
C:\Users\wittend.node-gyp\0.10.1\deps\v8\include\v8.h(184): warning
C4506: no definition for inline function 'v8::Persistent v8
::Persistent::New(v8::Handle)'
C:\Users\wittend.node-gyp\0.10.1\deps\v8\include\v8.h(184): warning
C4506: no definition for inline function 'v8::Persistent v8
::Persistent::New(v8::Handle)'
C:\Users\wittend.node-gyp\0.10.1\deps\v8\include\v8.h(179): warning
C4506: no definition for inline function 'v8::Persistent v8
::Persistent::New(v8::Handle)'
LINK : fatal error LNK1181: cannot open input file
'C:\Users\wittend.node-gyp\0.10.1\node.lib'
Project : warning PRJ0018: The following environment variables were not
found:
gyp ERR! build error
gyp ERR! stack Error:
C:\Windows\Microsoft.NET\Framework64\v3.5\msbuild.exe failed with
exit code: 1
gyp ERR! stack at ChildProcess.onExit (C:\Program
Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:256:23)
gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit
(child_process.js:754:12)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "node" "C:\Program

Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js"
"rebuild"
gyp ERR! cwd C:\Users\wittend\AppData\Roaming\npm\node_modules\ftdi
gyp ERR! node -v v0.10.1
gyp ERR! node-gyp -v v0.8.5
gyp ERR! not ok
npm ERR! ftdi@1.0.0 preinstall: node-gyp rebuild
npm ERR! cmd "/c" "node-gyp rebuild" failed with 1
npm ERR!
npm ERR! Failed at the ftdi@1.0.0 preinstall script.
npm ERR! This is most likely a problem with the ftdi package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls ftdi
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program
Files\nodejs\node_modules\npm\bin\npm-cli.js" "-g" "insta
ll" "ftdi"
npm ERR! cwd D:\Projects\code\web-csg
npm ERR! node -v v0.10.1
npm ERR! npm -v 1.2.15
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! D:\Projects\code\web-csg\npm-debug.log
npm ERR! not ok code 0
D:\Projects\code\web-csg>

Thanks,

Dave

@mscdex

This comment has been minimized.

Copy link
Contributor

@mscdex mscdex commented Mar 31, 2013

Can you please temporarily insert some debug statements into 'C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js' on this line (exact line number may be different) and re-run?:

console.log('buildType: ' + buildType);
console.log('nodeDir: ' + nodeDir);
console.log('arch: ' + arch);
console.log('buildDir: ' + buildDir);
console.log('archNodeLibPath: ' + archNodeLibPath);
console.log('buildNodeLibPath: ' + buildNodeLibPath);
@wittend

This comment has been minimized.

Copy link
Author

@wittend wittend commented Mar 31, 2013

mscdex,

Thanks for the response.

The full output with those lines inserted follows (attempting to install the ftdi module as global)>

Dave

== Console Output =================================

D:\Projects\code\web-csg>npm -g install ftdi
npm http GET https://registry.npmjs.org/ftdi
npm http 304 https://registry.npmjs.org/ftdi

ftdi@1.0.0 preinstall C:\Users\wittend\AppData\Roaming\npm\node_modules\ftdi
node-gyp rebuild

C:\Users\wittend\AppData\Roaming\npm\node_modules\ftdi>node "C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin....\node_modu
les\node-gyp\bin\node-gyp.js" rebuild
buildType: Release
nodeDir: C:\Users\wittend.node-gyp\0.10.2
arch: x64
buildDir: C:\Users\wittend.node-gyp\0.10.2\Release
archNodeLibPath: C:\Users\wittend.node-gyp\0.10.2\x64\node.lib
buildNodeLibPath: C:\Users\wittend.node-gyp\0.10.2\Release\node.lib
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\include\xlocale(342): warning C4530: C++ exception handler used, but unwind sema
ntics are not enabled. Specify /EHsc
C:\Users\wittend.node-gyp\0.10.2\deps\v8\include\v8.h(184): warning C4506: no definition for inline function 'v8::Persistent v8::P
ersistent::New(v8::Handle)'
C:\Users\wittend.node-gyp\0.10.2\deps\v8\include\v8.h(184): warning C4506: no definition for inline function 'v8::Persistent v8::P
ersistent::New(v8::Handle)'
C:\Users\wittend.node-gyp\0.10.2\deps\v8\include\v8.h(179): warning C4506: no definition for inline function 'v8::Persistent v8::P
ersistent::New(v8::Handle)'
LINK : fatal error LNK1181: cannot open input file 'C:\Users\wittend.node-gyp\0.10.2\node.lib'
Project : warning PRJ0018: The following environment variables were not found:
gyp ERR! build error
gyp ERR! stack Error: C:\Windows\Microsoft.NET\Framework\v3.5\msbuild.exe failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:273:23)
gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:757:12)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "node" "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\wittend\AppData\Roaming\npm\node_modules\ftdi
gyp ERR! node -v v0.10.2
gyp ERR! node-gyp -v v0.9.3
gyp ERR! not ok
npm ERR! ftdi@1.0.0 preinstall: node-gyp rebuild
npm ERR! cmd "/c" "node-gyp rebuild" failed with 1
npm ERR!
npm ERR! Failed at the ftdi@1.0.0 preinstall script.
npm ERR! This is most likely a problem with the ftdi package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls ftdi
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "-g" "install"
"ftdi"
npm ERR! cwd D:\Projects\code\web-csg
npm ERR! node -v v0.10.2
npm ERR! npm -v 1.2.15
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! D:\Projects\code\web-csg\npm-debug.log
npm ERR! not ok code 0

D:\Projects\code\web-csg>

== END of output =================================

== npm_debug.log:================================

0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli '-g',
1 verbose cli 'install',
1 verbose cli 'ftdi' ]
2 info using npm@1.2.15
3 info using node@v0.10.2
4 verbose node symlink C:\Program Files\nodejs\node.exe
5 verbose read json C:\Users\wittend\AppData\Roaming\npm\package.json
6 verbose read json C:\Users\wittend\AppData\Roaming\npm\package.json
7 verbose cache add [ 'ftdi', null ]
8 verbose cache add name=undefined spec="ftdi" args=["ftdi",null]
9 verbose parsed url { protocol: null,
9 verbose parsed url slashes: null,
9 verbose parsed url auth: null,
9 verbose parsed url host: null,
9 verbose parsed url port: null,
9 verbose parsed url hostname: null,
9 verbose parsed url hash: null,
9 verbose parsed url search: null,
9 verbose parsed url query: null,
9 verbose parsed url pathname: 'ftdi',
9 verbose parsed url path: 'ftdi',
9 verbose parsed url href: 'ftdi' }
10 silly lockFile 8188a8d8-ftdi ftdi
11 verbose lock ftdi C:\Users\wittend\AppData\Roaming\npm-cache\8188a8d8-ftdi.lock
12 silly lockFile 8188a8d8-ftdi ftdi
13 silly lockFile 8188a8d8-ftdi ftdi
14 verbose addNamed [ 'ftdi', '' ]
15 verbose addNamed [ null, '' ]
16 silly lockFile f375aa41-ftdi ftdi@
17 verbose lock ftdi@ C:\Users\wittend\AppData\Roaming\npm-cache\f375aa41-ftdi.lock
18 silly addNameRange { name: 'ftdi', range: '', hasData: false }
19 verbose url raw ftdi
20 verbose url resolving [ 'https://registry.npmjs.org/', './ftdi' ]
21 verbose url resolved https://registry.npmjs.org/ftdi
22 info trying registry request attempt 1 at 08:57:07
23 verbose etag "DX50JOXHWEVAV8WDZNXLCXXU3"
24 http GET https://registry.npmjs.org/ftdi
25 http 304 https://registry.npmjs.org/ftdi
26 silly registry.get cb [ 304,
26 silly registry.get { server: 'CouchDB/1.2.1 (Erlang OTP/R15B03)',
26 silly registry.get etag: '"DX50JOXHWEVAV8WDZNXLCXXU3"',
26 silly registry.get date: 'Sun, 31 Mar 2013 13:57:08 GMT',
26 silly registry.get 'content-length': '0' } ]
27 verbose etag ftdi from cache
28 silly addNameRange number 2 { name: 'ftdi', range: '', hasData: true }
29 silly addNameRange versions [ 'ftdi', [ '1.0.0' ] ]
30 verbose addNamed [ 'ftdi', '1.0.0' ]
31 verbose addNamed [ '1.0.0', '1.0.0' ]
32 silly lockFile 191355b1-ftdi-1-0-0 ftdi@1.0.0
33 verbose lock ftdi@1.0.0 C:\Users\wittend\AppData\Roaming\npm-cache\191355b1-ftdi-1-0-0.lock
34 verbose read json C:\Users\wittend\AppData\Roaming\npm-cache\ftdi\1.0.0\package\package.json
35 silly lockFile 191355b1-ftdi-1-0-0 ftdi@1.0.0
36 silly lockFile 191355b1-ftdi-1-0-0 ftdi@1.0.0
37 silly lockFile f375aa41-ftdi ftdi@
38 silly lockFile f375aa41-ftdi ftdi@
39 silly resolved [ { name: 'ftdi',
39 silly resolved version: '1.0.0',
39 silly resolved description: 'FTDI bindings for Node.js',
39 silly resolved main: 'index.js',
39 silly resolved dependencies: { bindings: '1.1.0' },
39 silly resolved scripts:
39 silly resolved { test: 'echo "Error: no test specified" && exit 1',
39 silly resolved preinstall: 'node-gyp rebuild' },
39 silly resolved repository:
39 silly resolved { type: 'git',
39 silly resolved url: 'git://github.com/KABA-CCEAC/node-ftdi.git' },
39 silly resolved keywords: [ 'ftdi', 'usb', 'driver', 'device' ],
39 silly resolved homepage: 'https://github.com/KABA-CCEAC/node-ftdi',
39 silly resolved bugs: { url: 'https://github.com/KABA-CCEAC/node-ftdi/issues' },
39 silly resolved license:
39 silly resolved { type: 'MIT',
39 silly resolved url: 'https://raw.github.com/KABA-CCEAC/node-ftdi/master/licence' },
39 silly resolved readme: '

\n  eeeee eeeee eeeee eeee       e  eeeee \n  8   8 8  88 8   8 8          8  8   " \n  8e  8 8   8 8e  8 8eee       8e 8eeee \n  88  8 8   8 88  8 88      e  88    88 \n  88  8 8eee8 88ee8 88ee 88 8ee88 8ee88\n\n  eeee eeeee eeeee e  \n  8      8   8   8 8  \n  8eee   8e  8e  8 8e \n  88     88  88  8 88 \n  88     88  88ee8 88 \n
\n\n# Installing\n\n## Prerequisites:\n\nInstall the driver: ftdi\n\nIf you're are using a Linux distribution or Mac OS X you can run the install.sh script file...\n\n\n npm install ftdi\n\nThis assumes you have everything on your system necessary to compile ANY native module for Node.js. This may not be the case, though, so please ensure the following are true for your system before filing an issue about "Does not install". For all operatings systems, please ensure you have Python 2.x installed AND not 3.0, node-gyp (what we use to compile) requires Python 2.x.\n\n### Windows:\n\nEnsure you have Visual Studio 2010 installed. If you have any version OTHER THAN VS 2010, please read this: #44 \n\n### Mac OS X:\n\nEnsure that you have at a minimum the xCode Command Line Tools installed appropriate for your system configuration. If you recently upgrade OS, it probably removed your installation of Command Line Tools, please verify before submitting a ticket.\n\n### Linux:\n\nYou know what you need for you system, basically your appropriate analog of build-essential. Keep rocking!\n\n\n# Usage\n\n## Listing or finding devices\n\nnodejs\nvar ftdi = require(\'ftdi\');\n\nftdi.find(0x27f4, 0x0203, function(err, devices) {}); // returns all ftdi devices with\n // matching vendor and product id\n\n\n## Create an FtdiDevice\n\nnodejs\nvar ftdi = require(\'ftdi\');\n\nvar device = new ftdi.FtdiDevice({\n locationId: 0,\n serialNumber: 0\n});\n\n// or\nvar device = new ftdi.FtdiDevice(0); // index in list function\n\n\n## All together\n\nnodejs\nvar ftdi = require(\'ftdi\');\n\nftdi.find(0x27f4, 0x0203, function(err, devices) {\n var device = new ftdi.FtdiDevice(devices[0]);\n\n device.on(\'error\', function(err) {\n });\n\n device.open({\n baudrate: 115200,\n databits: 8,\n stopbits: 1,\n parity: \'none\'\n },\n function(err) {\n\n device.on(\'data\', function(data) {\n\n });\n\n device.write([0x01, 0x02, 0x03, 0x04, 0x05], function(err) {\n\n });\n\n });\n\n});\n\n\n# Release Notes\n\n## v1.0.0\n\n- first release\n\n\n# License\n\nCopyright (c) 2013 Kaba AG\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the "Software"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in\nall copies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN\nTHE SOFTWARE.\n',
39 silly resolved readmeFilename: 'README.md',
39 silly resolved _id: 'ftdi@1.0.0',
39 silly resolved _from: 'ftdi@' } ]
40 info install ftdi@1.0.0 into C:\Users\wittend\AppData\Roaming\npm
41 info installOne ftdi@1.0.0
42 verbose from cache C:\Users\wittend\AppData\Roaming\npm-cache\ftdi\1.0.0\package\package.json
43 info C:\Users\wittend\AppData\Roaming\npm\node_modules\ftdi unbuild
44 verbose read json C:\Users\wittend\AppData\Roaming\npm\node_modules\ftdi\package.json
45 verbose tar unpack C:\Users\wittend\AppData\Roaming\npm-cache\ftdi\1.0.0\package.tgz
46 silly lockFile b2fd57a8-ta-Roaming-npm-node-modules-ftdi C:\Users\wittend\AppData\Roaming\npm\node_modules\ftdi
47 verbose lock C:\Users\wittend\AppData\Roaming\npm\node_modules\ftdi C:\Users\wittend\AppData\Roaming\npm-cache\b2fd57a8-ta-Roaming-npm-node-modules-ftdi.lock
48 silly lockFile 35a8219b-npm-cache-ftdi-1-0-0-package-tgz C:\Users\wittend\AppData\Roaming\npm-cache\ftdi\1.0.0\package.tgz
49 verbose lock C:\Users\wittend\AppData\Roaming\npm-cache\ftdi\1.0.0\package.tgz C:\Users\wittend\AppData\Roaming\npm-cache\35a8219b-npm-cache-ftdi-1-0-0-package-tgz.lock
50 silly gunzTarPerm modes [ '755', '644' ]
51 silly gunzTarPerm extractEntry package.json
52 silly gunzTarPerm modified mode [ 'package.json', 438, 420 ]
53 silly gunzTarPerm extractEntry .npmignore
54 silly gunzTarPerm modified mode [ '.npmignore', 438, 420 ]
55 silly gunzTarPerm extractEntry README.md
56 silly gunzTarPerm modified mode [ 'README.md', 438, 420 ]
57 silly gunzTarPerm extractEntry index.js
58 silly gunzTarPerm modified mode [ 'index.js', 438, 420 ]
59 silly gunzTarPerm extractEntry binding.gyp
60 silly gunzTarPerm modified mode [ 'binding.gyp', 438, 420 ]
61 silly gunzTarPerm extractEntry install.sh
62 silly gunzTarPerm modified mode [ 'install.sh', 438, 420 ]
63 silly gunzTarPerm extractEntry lib/amd64/ftd2xx.lib
64 silly gunzTarPerm modified mode [ 'lib/amd64/ftd2xx.lib', 438, 420 ]
65 silly gunzTarPerm extractEntry lib/ftd2xx.h
66 silly gunzTarPerm modified mode [ 'lib/ftd2xx.h', 438, 420 ]
67 silly gunzTarPerm extractEntry lib/i386/ftd2xx.lib
68 silly gunzTarPerm modified mode [ 'lib/i386/ftd2xx.lib', 438, 420 ]
69 silly gunzTarPerm extractEntry license
70 silly gunzTarPerm modified mode [ 'license', 438, 420 ]
71 silly gunzTarPerm extractEntry src/ftdi_constants.h
72 silly gunzTarPerm modified mode [ 'src/ftdi_constants.h', 438, 420 ]
73 silly gunzTarPerm extractEntry src/ftdi_device.cc
74 silly gunzTarPerm modified mode [ 'src/ftdi_device.cc', 438, 420 ]
75 silly gunzTarPerm extractEntry src/ftdi_device.h
76 silly gunzTarPerm modified mode [ 'src/ftdi_device.h', 438, 420 ]
77 silly gunzTarPerm extractEntry src/ftdi_driver.cc
78 silly gunzTarPerm modified mode [ 'src/ftdi_driver.cc', 438, 420 ]
79 silly gunzTarPerm extractEntry src/ftdi_driver.h
80 silly gunzTarPerm modified mode [ 'src/ftdi_driver.h', 438, 420 ]
81 verbose read json C:\Users\wittend\AppData\Roaming\npm\node_modules\ftdi\package.json
82 silly lockFile b2fd57a8-ta-Roaming-npm-node-modules-ftdi C:\Users\wittend\AppData\Roaming\npm\node_modules\ftdi
83 silly lockFile b2fd57a8-ta-Roaming-npm-node-modules-ftdi C:\Users\wittend\AppData\Roaming\npm\node_modules\ftdi
84 silly lockFile 35a8219b-npm-cache-ftdi-1-0-0-package-tgz C:\Users\wittend\AppData\Roaming\npm-cache\ftdi\1.0.0\package.tgz
85 silly lockFile 35a8219b-npm-cache-ftdi-1-0-0-package-tgz C:\Users\wittend\AppData\Roaming\npm-cache\ftdi\1.0.0\package.tgz
86 info preinstall ftdi@1.0.0
87 verbose unsafe-perm in lifecycle true
88 silly exec cmd "/c" "node-gyp rebuild"
89 silly cmd,/c,node-gyp rebuild,C:\Users\wittend\AppData\Roaming\npm\node_modules\ftdi spawning
90 info ftdi@1.0.0 Failed to exec preinstall script
91 info C:\Users\wittend\AppData\Roaming\npm\node_modules\ftdi unbuild
92 verbose from cache C:\Users\wittend\AppData\Roaming\npm\node_modules\ftdi\package.json
93 info preuninstall ftdi@1.0.0
94 info uninstall ftdi@1.0.0
95 verbose true,C:\Users\wittend\AppData\Roaming\npm\node_modules,C:\Users\wittend\AppData\Roaming\npm\node_modules unbuild ftdi@1.0.0
96 info postuninstall ftdi@1.0.0
97 error ftdi@1.0.0 preinstall: node-gyp rebuild
97 error cmd "/c" "node-gyp rebuild" failed with 1
98 error Failed at the ftdi@1.0.0 preinstall script.
98 error This is most likely a problem with the ftdi package,
98 error not with npm itself.
98 error Tell the author that this fails on your system:
98 error node-gyp rebuild
98 error You can get their info via:
98 error npm owner ls ftdi
98 error There is likely additional logging output above.
99 error System Windows_NT 6.1.7601
100 error command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "-g" "install" "ftdi"
101 error cwd D:\Projects\code\web-csg
102 error node -v v0.10.2
103 error npm -v 1.2.15
104 error code ELIFECYCLE
105 verbose exit [ 1, true ]

== END of output =================================

@wittend wittend closed this Mar 31, 2013
@mscdex mscdex reopened this Mar 31, 2013
@mscdex

This comment has been minimized.

Copy link
Contributor

@mscdex mscdex commented Mar 31, 2013

Ok it seems the problem lies earlier, please add a few more lines:

In lib/configure.js, add this after this line:

console.log('nodeDir: ' + nodeDir);
console.log('gyp.devDir: ' + gyp.devDir);

In lib/node-gyp.js, add this on this line:

console.log('homeDir: ' + homeDir);
@wittend

This comment has been minimized.

Copy link
Author

@wittend wittend commented Mar 31, 2013

Ok,

That gets:

D:\Projects\code\web-csg>npm -g install ftdi
npm http GET https://registry.npmjs.org/ftdi
npm http 304 https://registry.npmjs.org/ftdi

ftdi@1.0.0 preinstall
C:\Users\wittend\AppData\Roaming\npm\node_modules\ftdi
node-gyp rebuild

C:\Users\wittend\AppData\Roaming\npm\node_modules\ftdi>node "C:\Program
Files\nodejs\node_modules\npm\bin\node-gyp-bin....\node_modu
les\node-gyp\bin\node-gyp.js" rebuild
homeDir: C:\Users\wittend
nodeDir: C:\Users\wittend.node-gyp\0.10.2
gyp.devDir: C:\Users\wittend.node-gyp
buildType: Release
nodeDir: C:\Users\wittend.node-gyp\0.10.2
arch: x64
buildDir: C:\Users\wittend.node-gyp\0.10.2\Release
archNodeLibPath: C:\Users\wittend.node-gyp\0.10.2\x64\node.lib
buildNodeLibPath: C:\Users\wittend.node-gyp\0.10.2\Release\node.lib
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\include\xlocale(342):
warning C4530: C++ exception handler used, but unwind sema
ntics are not enabled. Specify /EHsc
C:\Users\wittend.node-gyp\0.10.2\deps\v8\include\v8.h(184): warning C4506:
no definition for inline function 'v8::Persistent v8::P
ersistent::New(v8::Handle)'
C:\Users\wittend.node-gyp\0.10.2\deps\v8\include\v8.h(184): warning C4506:
no definition for inline function 'v8::Persistent v8::P
ersistent::New(v8::Handle)'
C:\Users\wittend.node-gyp\0.10.2\deps\v8\include\v8.h(179): warning C4506:
no definition for inline function 'v8::Persistent v8::P
ersistent::New(v8::Handle)'
LINK : fatal error LNK1181: cannot open input file
'C:\Users\wittend.node-gyp\0.10.2\node.lib'
Project : warning PRJ0018: The following environment variables were not
found:
gyp ERR! build error
gyp ERR! stack Error: C:\Windows\Microsoft.NET\Framework\v3.5\msbuild.exe
failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (C:\Program
Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:273:23)
gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit
(child_process.js:757:12)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "node" "C:\Program
Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js"
"rebuild"
gyp ERR! cwd C:\Users\wittend\AppData\Roaming\npm\node_modules\ftdi
gyp ERR! node -v v0.10.2
gyp ERR! node-gyp -v v0.9.3
gyp ERR! not ok
npm ERR! ftdi@1.0.0 preinstall: node-gyp rebuild
npm ERR! cmd "/c" "node-gyp rebuild" failed with 1
npm ERR!
npm ERR! Failed at the ftdi@1.0.0 preinstall script.
npm ERR! This is most likely a problem with the ftdi package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls ftdi
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program
Files\nodejs\node_modules\npm\bin\npm-cli.js" "-g" "install"
"ftdi"
npm ERR! cwd D:\Projects\code\web-csg
npm ERR! node -v v0.10.2
npm ERR! npm -v 1.2.15
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! D:\Projects\code\web-csg\npm-debug.log
npm ERR! not ok code 0

D:\Projects\code\web-csg>

at the console...

Dave

On Sun, Mar 31, 2013 at 9:28 AM, Brian White notifications@github.comwrote:

Ok it seems the problem lies earlier, please add a few more lines:

In lib/configure.js, add this after this linehttps://github.com/TooTallNate/node-gyp/blob/master/lib/configure.js#L222
:

console.log('nodeDir: ' + nodeDir);console.log('gyp.devDir: ' + gyp.devDir);

In lib/node-gyp.js, add this on this linehttps://github.com/TooTallNate/node-gyp/blob/master/lib/node-gyp.js#L50
:

console.log('homeDir: ' + homeDir);


Reply to this email directly or view it on GitHubhttps://github.com//issues/227#issuecomment-15691994
.

@mscdex

This comment has been minimized.

Copy link
Contributor

@mscdex mscdex commented Mar 31, 2013

Odd.... did anything change since the last time you ran the install? The path seems to include the backslash now....

@wittend

This comment has been minimized.

Copy link
Author

@wittend wittend commented Mar 31, 2013

Brian,

I'm not quite sure what it is you are looking at. Nothing has changed
today. I keep running the same command lines in the same console window.
I'm not doing anything else related to this. just reading email.

the line:

LINK : fatal error LNK1181: cannot open input file
'C:\Users\wittend.node-gyp\0.10.2\node.lib'

seems the same. It appears that 'Arch' should be getting substituted into
this link line as in "'C:\Users\wittend.node-gyp\x64\node.lib", but beyond
that I don't know what is going on.

Dave

On Sun, Mar 31, 2013 at 9:49 AM, Brian White notifications@github.comwrote:

Odd.... did anything change since the last time you ran the install? The
path seems to include the backslash now....


Reply to this email directly or view it on GitHubhttps://github.com//issues/227#issuecomment-15692244
.

@mscdex

This comment has been minimized.

Copy link
Contributor

@mscdex mscdex commented Apr 1, 2013

@wittend Previously the output you posted had showed: 'C:\Users\wittend.node-gyp\0.10.2\node.lib' (specifically the missing backslash after your username).

@wittend

This comment has been minimized.

Copy link
Author

@wittend wittend commented Apr 1, 2013

Brian,

Thanks for looking at it for me. I looked myself some more, and I'm back
to thinking that the problem lies in the packages I'm trying to install,
perhaps. Almost all of them fail, mostly in the same way, but there are
some variations. All of them involve interfacing to USB and/or serial
ports on Windows. Very frustrating. Perhaps there has been some basic
change to node-gyp over time and they have not updated their setup. And
perhaps that is why many of them are forks of earlier ones.

I may just have to make my own de novo. So much for code re usability.

Dave

On Sun, Mar 31, 2013 at 11:46 PM, Brian White notifications@github.comwrote:

@wittend https://github.com/wittend Previously the output you posted
had showed: 'C:\Users\wittend.node-gyp\0.10.2\node.lib' (specifically the
missing backslash after your username).


Reply to this email directly or view it on GitHubhttps://github.com//issues/227#issuecomment-15704202
.

@mscdex

This comment has been minimized.

Copy link
Contributor

@mscdex mscdex commented Apr 4, 2013

@wittend I'm not so sure it's the individual packages. For example: I can install the 'ftdi' package without issue on my desktop (with Windows 7, VC2010 Express, Windows 7.1 SDK, plain command prompt, node v0.10.x).

@wittend

This comment has been minimized.

Copy link
Author

@wittend wittend commented Apr 4, 2013

Brian,

Perhaps you're right. Either way, I'm frustrated with this, and it has
put me off Nodejs for the moment. Everything that I want to do seems to
need node-gyp to compile something, so I'm twisting in the wind.

Dave

On Thu, Apr 4, 2013 at 12:34 AM, Brian White notifications@github.comwrote:

@wittend https://github.com/wittend I'm not so sure it's the individual
packages. For example: I can install the 'ftdi' package without issue on my
desktop (with Windows 7, VC2010 Express, Windows 7.1 SDK, plain command
prompt, node v0.10.x).


Reply to this email directly or view it on GitHubhttps://github.com//issues/227#issuecomment-15880678
.

@tinjaw

This comment has been minimized.

Copy link

@tinjaw tinjaw commented Apr 7, 2013

I am seeing this too as well. It looks like some environmental variable needs to be set; in fact something is even mentioned in the error, but it doesn't give the variable. If there was some environmental variable and it was set to the architecture, then it would probably insert the proper string between the two backslashes and it would be fine.

C:\client\node_modules\upnode\node_modules\dnode\node_modules\weak>node "C:\nodejs\node_modules\npm\bin\node-gyp-bin\\..
\..\node_modules\node-gyp\bin\node-gyp.js" rebuild
C:\Users\ckrause\.node-gyp\0.10.3\deps\v8\include\v8.h(184): warning C4506: no definition for inline function 'v8::Pers
istent<T> v8::Persistent<T>::New(v8::Handle<T>)'
LINK : fatal error LNK1181: cannot open input file 'C:\Users\ckrause\.node-gyp\0.10.3\\node.lib'
Project : warning PRJ0018: The following environment variables were not found:
gyp ERR! build error
gyp ERR! stack Error: `msbuild` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:267:23)
gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:786:12)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "node" "C:\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\client\node_modules\upnode\node_modules\dnode\node_modules\weak
gyp ERR! node -v v0.10.3
gyp ERR! node-gyp -v v0.9.5
gyp ERR! not ok
npm ERR! weak@0.2.2 install: `node-gyp rebuild`
npm ERR! `cmd "/c" "node-gyp rebuild"` failed with 1
npm ERR!
@mscdex

This comment has been minimized.

Copy link
Contributor

@mscdex mscdex commented Apr 7, 2013

@tinjaw Can you try applying this patch and see if it gives you the rest of the error message?

@tinjaw

This comment has been minimized.

Copy link

@tinjaw tinjaw commented Apr 7, 2013

I have moved on in order to complete my current project. I will attempt to
reproduce ASAP and report back.

On Sun, Apr 7, 2013 at 2:07 PM, Brian White notifications@github.comwrote:

@tinjaw https://github.com/tinjaw Can you try applying this patchhttps://gist.github.com/mscdex/683f4d47088ccfac2f49and see if it gives you the rest of the error message?


Reply to this email directly or view it on GitHubhttps://github.com//issues/227#issuecomment-16021287
.

@wittend

This comment has been minimized.

Copy link
Author

@wittend wittend commented May 8, 2013

Packages requiring node-gyp remain the roadblock to me using nodejs for anything on Windows.

I thought that I would revisit this problem to see if anything has improved.

I am using Win 7 Ultimate 32 bit with SP1 on an older HP Centrino Duo laptop. Nothing special, nothing weird.

I removed everything that seemed in any way related to this problem. Visual studio 10, Windows SDK, related service packs, node-gyp and finally node itself. Then I set about re-installing everything on this machine exactly by-the-book. I installed Node 10.5 and node-gyp 9.5 using 'npm -g install xxx'. I installed Visual Studio C++ 2010 and the Windows SDK from the links on the node-gyp page in the NPM registry. I instaled the VC++ SP1 as well, as mentioned for 64 bit builds, because the SDK install failed without it (though I am doing 32 bit builds).

As in all previous attempts, efforts to install any packages dependent on node-gyp failed. The reported errors vary slightly, but always point to node-gyp and usually take a form such as:

C:\Users\New\AppData\Roaming\npm\node_modules\usb>node "C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js"
ild
cl : Command line warning D9025: overriding '/MT' with '/MD' [C:\Users\New\AppData\Roaming\npm\node_modules\usb\build\usb_bindings.vcxproj]
cl : Command line warning D9025: overriding '/MT' with '/MD' [C:\Users\New\AppData\Roaming\npm\node_modules\usb\build\usb_bindings.vcxproj]
  transfer.cc
cl : Command line warning D9025: overriding '/MT' with '/MD' [C:\Users\New\AppData\Roaming\npm\node_modules\usb\build\usb_bindings.vcxproj]
  node_usb.cc
c:\Program Files\Microsoft Visual Studio 10.0\VC\include\intrin.h(26): fatal error C1083: Cannot open include file: 'ammintrin.h': No such file or directory [C:
ers\New\AppData\Roaming\npm\node_modules\usb\build\usb_bindings.vcxproj]
c:\Program Files\Microsoft Visual Studio 10.0\VC\include\intrin.h(26): fatal error C1083: Cannot open include file: 'ammintrin.h': No such file or directory [C:
ers\New\AppData\Roaming\npm\node_modules\usb\build\usb_bindings.vcxproj]
  device.cc
c:\Program Files\Microsoft Visual Studio 10.0\VC\include\intrin.h(26): fatal error C1083: Cannot open include file: 'ammintrin.h': No such file or directory [C:
ers\New\AppData\Roaming\npm\node_modules\usb\build\usb_bindings.vcxproj]
gyp ERR! build error
gyp ERR! stack Error: `C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:267:23)
gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:784:12)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "node" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\New\AppData\Roaming\npm\node_modules\usb
gyp ERR! node -v v0.10.5
gyp ERR! node-gyp -v v0.9.5
gyp ERR! not ok
npm ERR! usb@0.2.1 preinstall: `node-gyp rebuild`
npm ERR! `cmd "/c" "node-gyp rebuild"` failed with 1
npm ERR!
npm ERR! Failed at the usb@0.2.1 preinstall script.
npm ERR! This is most likely a problem with the usb package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls usb
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "-g" "install" "usb"
npm ERR! cwd C:\Users\New
npm ERR! node -v v0.10.5
npm ERR! npm -v 1.2.18
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     C:\Users\New\npm-debug.log
npm ERR! not ok code 0

I really don't know what the problem is, but it has totally put me off using node.js. If a package as pervasive and necessary as node-gyp cannot be counted on to work, the entire node ecosystem must be considered too fragile for useful work.

@TooTallNate

This comment has been minimized.

Copy link
Contributor

@TooTallNate TooTallNate commented May 8, 2013

@wittend Your particular error it looks like is a problem on Microsoft's end: http://connect.microsoft.com/VisualStudio/feedback/details/660584/ (p.s. google is your friend...)

@wittend

This comment has been minimized.

Copy link
Author

@wittend wittend commented May 12, 2013

Yes, I had spent a lot of time with google before I posted this. My
primary intent was to let you know that your posted links were useless.
And MS seems to have no intention of fixing this. The suggested
workarounds do not work for my situation, so using any package dependent on
node-gyp is dead on the pavement. The glory of the source-only
distribution model!

-Dave

On Wed, May 8, 2013 at 2:48 PM, Nathan Rajlich notifications@github.comwrote:

@wittend https://github.com/wittend Your particular error it looks like
is a problem on Microsoft's end:
http://connect.microsoft.com/VisualStudio/feedback/details/660584/ (p.s.
google is your friend...)


Reply to this email directly or view it on GitHubhttps://github.com//issues/227#issuecomment-17629415
.

@TooTallNate

This comment has been minimized.

Copy link
Contributor

@TooTallNate TooTallNate commented May 13, 2013

Well the thing is, myself and many others have gotten the proper
dependencies for node-gyp installed on their Windows boxes, so it sounds
like a configuration problem on your end to me. I'm sorry I can't be more
specific but these errors are hard to debug when I can't reproduce them
myself.

On Sun, May 12, 2013 at 4:56 PM, Dave notifications@github.com wrote:

Yes, I had spent a lot of time with google before I posted this. My
primary intent was to let you know that your posted links were useless.
And MS seems to have no intention of fixing this. The suggested
workarounds do not work for my situation, so using any package dependent
on
node-gyp is dead on the pavement. The glory of the source-only
distribution model!

-Dave

On Wed, May 8, 2013 at 2:48 PM, Nathan Rajlich notifications@github.comwrote:

@wittend https://github.com/wittend Your particular error it looks
like
is a problem on Microsoft's end:
http://connect.microsoft.com/VisualStudio/feedback/details/660584/(p.s.
google is your friend...)


Reply to this email directly or view it on GitHub<
https://github.com/TooTallNate/node-gyp/issues/227#issuecomment-17629415>
.


Reply to this email directly or view it on GitHubhttps://github.com//issues/227#issuecomment-17787948
.

@wittend

This comment has been minimized.

Copy link
Author

@wittend wittend commented May 13, 2013

Is there no option to use another compiler? Microsoft explicitly states
that they have no intention of fixing the one your links indicate. I do
almost all my windows work with MinGW. But that version of the MS V Studio
full compiler is unavailable to me because it is very out of date. It is
simply missing a single header file, as far as I can tell, and that is
nowhere to be found.

Dave

On Sun, May 12, 2013 at 7:04 PM, Nathan Rajlich notifications@github.comwrote:

Well the thing is, myself and many others have gotten the proper
dependencies for node-gyp installed on their Windows boxes, so it sounds
like a configuration problem on your end to me. I'm sorry I can't be more
specific but these errors are hard to debug when I can't reproduce them
myself.

On Sun, May 12, 2013 at 4:56 PM, Dave notifications@github.com wrote:

Yes, I had spent a lot of time with google before I posted this. My
primary intent was to let you know that your posted links were useless.
And MS seems to have no intention of fixing this. The suggested
workarounds do not work for my situation, so using any package dependent
on
node-gyp is dead on the pavement. The glory of the source-only
distribution model!

-Dave

On Wed, May 8, 2013 at 2:48 PM, Nathan Rajlich notifications@github.comwrote:

@wittend https://github.com/wittend Your particular error it looks
like
is a problem on Microsoft's end:
http://connect.microsoft.com/VisualStudio/feedback/details/660584/(p.s.

google is your friend...)


Reply to this email directly or view it on GitHub<
https://github.com/TooTallNate/node-gyp/issues/227#issuecomment-17629415>

.


Reply to this email directly or view it on GitHub<
https://github.com/TooTallNate/node-gyp/issues/227#issuecomment-17787948>
.


Reply to this email directly or view it on GitHubhttps://github.com//issues/227#issuecomment-17788078
.

@brysmi

This comment has been minimized.

Copy link

@brysmi brysmi commented Jun 13, 2013

I think you are correct -- it has come down to one particular header file missing, and the return on investing more time has become trivial. Back to the Java/Python mines!

@fed79

This comment has been minimized.

Copy link

@fed79 fed79 commented Jun 24, 2013

Hi guys, I got this sorted out and hope that it will work for you too.

Had the exact same problem, Win7 / 64 / Ultimate and was missing the ammintrin.h file
basically fixing it comes down to installing VS2010 SP1

source:
http://wishmesh.com/2011/04/fatal-error-c1083-cannot-open-include-file-ammintrin-h-no-such-file-or-directory/

Federico

@JayBeavers

This comment has been minimized.

Copy link
Contributor

@JayBeavers JayBeavers commented Dec 10, 2013

Much work has gone into fixing node-gyp on Windows recently. Now we're down to awaiting a final integration into node (gyp and node-gyp and npm are now all up to date) and then things should work much smoother.

Please also update to Visual Studio 2013 Express for Windows Desktop. In addition to the compatibility fixes in NodeJS, you'll find the new C++ compiler is improved and more standards compliant.

My apologies for the challenges you've faced. Be aware that NodeJS isn't a Microsoft supported product and much of its support is done through personal contributions off the clock. Also be aware that VS 2010 is pretty old and didn't even support x64 well in its initial release.

@wittend

This comment has been minimized.

Copy link
Author

@wittend wittend commented Dec 10, 2013

@JayBeavers,

Thank you for the update. This has remained an obstacle to my use of NodeJS.

"you'll find the new C++ compiler is improved and more standards compliant" - an issue since Microsoft engulfed and consumed Lattice C 2.0 and spit MSC 2.0 out in its place way back in the day.

I will try the new compiler.

Dave

@stevemcallister

This comment has been minimized.

Copy link

@stevemcallister stevemcallister commented Dec 29, 2013

Hey,

I am just a guy trying to get his Arduino board to be programmed in JavaScript. In my attempt to follow the instructions from the #1 Google SERP results for arduino javascript https://www.google.com/search?q=arduino+javascript. I don't know JavaScript as well as I want, and I wanted a way to make it interesting to learn how to get some hardware to work with JS. In addition I do a lot of web programming in PHP, Classic ASP and C##. I had considered looking into trying out Node.js, again trying to become more familiar with JS. HOWEVER, after all of this farting around, I believe I might as well just go straight to C++, since it's essentially what I am trying to do anyway using JS. Am I wrong?

Anyways here is what working for me in getting node-gyp working on Windows XP, even though I really did not know it was node-gyp that was the issue till I dug further and read the install output a bit closer.

I found this post while looking for getting an Arduino board + Node.js + Johnny-Five working on my WinXP laptop. I just want to use JavaScript as the language for programming Arduino boards. My first attempt failed because I had a Full version of VS2008 and apparently that C++ compiler is not compatible, nor is the CygWin one.

I am new to the node.js scene, so I don't know the genesis of the project. But I can say that I am a bit disappointed in all of the parts needed and that there isn't a configure-esque way of a build attempt that will fail "early and often" if the dependent sub-systems are not compatible.

I found through trial and error that I needed a non-Cygwin V2.x Python (v2.7.6 from Python.org) and VS2010 Express C++. I also installed the SP1 before trying to do anything and ran MS Update a second time just in case. I was able install Johnny-Five, but I got warnings. The node command used to install is "npm install johnny-five"

There are a bunch of "npm http GET https://xxx" statements

Then

serialport@1.2.5 install C:\DEV\arduino-1.0.5\node_modules\johnny-five\node_modules\serialport
node-gyp rebuild

The node-gyp rebuild runs this in the current Windows command window

C$>node "C:\Apps\NodeJS\node_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
serialport.cpp
serialport_win.cpp
c:\Program Files\Microsoft Visual Studio 10.0\VC\include\xlocale(323): warning C4530: C++ exception handler used, but unwind semantics are not enabled. Specify /EHsc [C:\DEV\arduino-1.0.5\node_modules\johnny-five\node_modules\serialport\build\serialport.vcxproj]
c:\Program Files\Microsoft Visual Studio 10.0\VC\include\xlocale(323): warning C4530: C++ exception handler used, but unwind semantics are not enabled. Specify /EHsc [C:\DEV\arduino-1.0.5\node_modules\johnny-five\node_modules\serialport\build\serialport.vcxproj]
C:\Documents and Settings\smcallister.node-gyp\0.10.24\deps\v8\include\v8.h(184): warning C4506: no definition for inline function 'v8::Persistent v8::Persistent::New(v8::Handle)' [C:\DEV\arduino-1.0.5\node_modules\johnny-five\node_modules\serialport\build\serialport.vcxproj]
with
[
T=v8::Object
]
enumser.cpp
c:\Program Files\Microsoft Visual Studio 10.0\VC\include\xlocale(323): warning C4530: C++ exception handler used, but unwind semantics are not enabled. Specify /EHsc [C:\DEV\arduino-1.0.5\node_modules\johnny-five\node_modules\serialport\build\serialport.vcxproj]
C:\Documents and Settings\smcallister.node-gyp\0.10.24\deps\v8\include\v8.h(184): warning C4506: no definition for inline function 'v8::Persistent v8::Persistent::New(v8::Handle)' [C:\DEV\arduino-1.0.5\node_modules\johnny-five\node_modules\serialport\build\serialport.vcxproj]
with
[
T=v8::Object
]
disphelper.c
Creating library C:\DEV\arduino-1.0.5\node_modules\johnny-five\node_modules\serialport\build\Release\serialport.lib and object C:\DEV\arduino-1.0.5\node_modules\johnny-five\node_modules\serialport\build\Release\serialport.exp
Generating code
Finished generating code
serialport.vcxproj -> C:\DEV\arduino-1.0.5\node_modules\johnny-five\node_modules\serialport\build\Release\serialport.node
johnny-five@0.7.10 node_modules\johnny-five
├── nanotimer@0.3.0
├── compulsive@0.3.1
├── colors@0.6.2
├── temporal@0.2.10
├── descriptor@0.1.0
├── es6-collections@0.2.0
├── lodash@2.4.1
├── firmata@0.3.1 (browser-serialport@0.0.4)
└── serialport@1.2.5 (bindings@1.1.1, sf@0.1.6, async@0.1.18, optimist@0.3.7)

C$>

These are 2 of the 3 warning - are these something I can fix without too much trouble?

  1. c:\Program Files\Microsoft Visual Studio 10.0\VC\include\xlocale(323): warning C4530: C++ exception handler used, but unwind semantics are not enabled. Specify /EHsc [C:\DEV\arduino-1.0.5\node_modules\johnny-five\node_modules\serialport\build\serialport.vcxproj]

  2. C:\Documents and Settings\smcallister.node-gyp\0.10.24\deps\v8\include\v8.h(184): warning C4506: no definition for inline function 'v8::Persistent v8::Persistent::New(v8::Handle)' [C:\DEV\arduino-1.0.5\node_modules\johnny-five\node_modules\serialport\build\serialport.vcxproj]
    with
    [
    T=v8::Object
    ]
    enumser.cpp

Thanks,
--Steve

@Trott

This comment has been minimized.

Copy link
Member

@Trott Trott commented Mar 13, 2018

Seems like this issue is stale and probably resolved? Closable? @nodejs/node-gyp

@brysmi

This comment has been minimized.

Copy link

@brysmi brysmi commented Mar 13, 2018

@Trott

This comment has been minimized.

Copy link
Member

@Trott Trott commented Mar 13, 2018

Closing for now. Please comment or re-open if appropriate.

@Trott Trott closed this Mar 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
9 participants
You can’t perform that action at this time.