Not sure why that, but I've found a newer work-around to the original problem that avoids editing configure.js:
TERM=dumb npm install -g bonescript On Thu, Jan 9, 2014 at 1:34 PM, <[email protected]> wrote: > I know that this is an old thread now, but I had the same problems, followed > this solution and now I am getting an error about node-gyp failing to import > module filecmp. Any ideas? > > Thanks, Josh > > > On Wednesday, June 19, 2013 8:41:01 AM UTC-5, Jason Kridner wrote: >> >> B, >> >> I got tired of looking for your e-mail on the mailing list, so I'll just >> put the list in reply. This is the danger of e-mailing me support questions >> directly--not something I like too much. >> >> On Tue, Jun 18, 2013 at 7:29 PM, B Parvizi <[email protected]> wrote: >>> >>> Hi, >>> >>> I was trying to install bonescript using npm, and I receive the following >>> error below. I can get the updated code using: >>> >>> opkg update >>> opkg install bonescript >>> >>> but was hoping I could use npm so I can list bonescript as a dependency >>> in my packages.json file. Any help would be appreciated, thanks. Here is >>> the error: >>> >>> root@beaglebone:/var/lib/cloud9/bb-servo-example# npm install bonescript >>> --save >>> npm WARN package.json [email protected] No README.md file found! >>> npm http GET http://registry.npmjs.org/bonescript >>> npm http 304 http://registry.npmjs.org/bonescript >>> >>> > [email protected] preinstall >>> > /var/lib/cloud9/bb-servo-example/node_modules/bonescript >>> > node-gyp clean || (exit 0); node-gyp configure build >>> >>> gyp ERR! configure error >>> gyp ERR! stack Error: Python executable "python" is v2.7.3, which is not >>> supported by gyp. >>> gyp ERR! stack You can pass the --python switch to point to Python >= >>> v2.5.0 & < 3.0.0. >>> gyp ERR! stack at failPythonVersion >>> (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:118:14) >>> gyp ERR! stack at >>> /usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:107:9 >>> gyp ERR! stack at ChildProcess.exithandler (child_process.js:538:7) >>> gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:99:17) >>> gyp ERR! stack at maybeClose (child_process.js:638:16) >>> gyp ERR! stack at Process._handle.onexit (child_process.js:680:5) >> >> >> I added a couple of debug commands to >> /usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js and found >> that 'semver.lt' returns false when comparing 2.7.3 and 3.0.0. This is a >> bug in semver/node-gyp and not BoneScript. I simply commented out the >> comparison and the build completed for me. >> >> Note, you do need to perform the following steps for node-gyp to run on an >> Angstrom install that might not already have python-compiler: >> # opkg update >> # opkg install python-compiler >> >>> >>> gyp ERR! System Linux 3.8.13 >>> gyp ERR! command "node" >>> "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" >>> "configure" "build" >>> gyp ERR! cwd /var/lib/cloud9/bb-servo-example/node_modules/bonescript >>> gyp ERR! node -v v0.8.22 >>> gyp ERR! node-gyp -v v0.8.5 >>> gyp ERR! not ok >>> npm ERR! [email protected] preinstall: `node-gyp clean || (exit 0); >>> node-gyp configure build` >>> npm ERR! `sh "-c" "node-gyp clean || (exit 0); node-gyp configure build"` >>> failed with 1 >>> npm ERR! >>> npm ERR! Failed at the [email protected] preinstall script. >>> npm ERR! This is most likely a problem with the bonescript package, >>> npm ERR! not with npm itself. >>> npm ERR! Tell the author that this fails on your system: >>> npm ERR! node-gyp clean || (exit 0); node-gyp configure build >>> npm ERR! You can get their info via: >>> npm ERR! npm owner ls bonescript >>> npm ERR! There is likely additional logging output above. >>> >>> npm ERR! System Linux 3.8.13 >>> npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install" "bonescript" >>> "--save" >>> npm ERR! cwd /var/lib/cloud9/bb-servo-example >>> npm ERR! node -v v0.8.22 >>> npm ERR! npm -v 1.2.14 >>> npm ERR! code ELIFECYCLE >>> npm ERR! >>> npm ERR! Additional logging details can be found in: >>> npm ERR! /var/lib/cloud9/bb-servo-example/npm-debug.log >>> npm ERR! not ok code 0 >>> >>> >> > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
