Installation Failing (on Linux, Windows or Heroku etc.)

[jedfoster]

Error:

-----> Rebuilding any native dependencies

       > node-sass@1.0.1 install /tmp/build_3550e8f7-0269-4253-a8cf-f39ff7f9d0fb/node_modules/node-sass
       > node build.js

       `linux-x64-v8-3.14` exists; testing
       make: Entering directory `/tmp/build_3550e8f7-0269-4253-a8cf-f39ff7f9d0fb/node_modules/node-sass/build'
         CXX(target) Release/obj.target/binding/binding.o
       cc1plus: error: unrecognized command line option "-std=c++11"
       cc1plus: error: unrecognized command line option "-std=c++11"
       make: *** [Release/obj.target/binding/binding.o] Error 1
       make: Leaving directory `/tmp/build_3550e8f7-0269-4253-a8cf-f39ff7f9d0fb/node_modules/node-sass/build'
       gyp ERR! build error
       gyp ERR! stack Error: `make` failed with exit code: 2
       gyp ERR! stack     at ChildProcess.onExit (/tmp/build_3550e8f7-0269-4253-a8cf-f39ff7f9d0fb/vendor/node/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23)
       gyp ERR! stack     at ChildProcess.emit (events.js:98:17)
       gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:810:12)
       gyp ERR! System Linux 3.8.11-ec2
       gyp ERR! command "node" "/tmp/build_3550e8f7-0269-4253-a8cf-f39ff7f9d0fb/vendor/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
       gyp ERR! cwd /tmp/build_3550e8f7-0269-4253-a8cf-f39ff7f9d0fb/node_modules/node-sass
       gyp ERR! node -v v0.10.32
       gyp ERR! node-gyp -v v1.0.1
       gyp ERR! not ok
       Build failed

       npm ERR! node-sass@1.0.1 install: `node build.js`
       npm ERR! Exit status 1
       npm ERR!
       npm ERR! Failed at the node-sass@1.0.1 install script.
       npm ERR! This is most likely a problem with the node-sass package,
       npm ERR! not with npm itself.
       npm ERR! Tell the author that this fails on your system:
       npm ERR!     node build.js
       npm ERR! You can get their info via:
       npm ERR!     npm owner ls node-sass
       npm ERR! There is likely additional logging output above.
       npm ERR! System Linux 3.8.11-ec2
       npm ERR! command "/tmp/build_3550e8f7-0269-4253-a8cf-f39ff7f9d0fb/vendor/node/bin/node" "/tmp/build_3550e8f7-0269-4253-a8cf-f39ff7f9d0fb/vendor/node/bin/npm" "rebuild"
       npm ERR! cwd /tmp/build_3550e8f7-0269-4253-a8cf-f39ff7f9d0fb
       npm ERR! node -v v0.10.32
       npm ERR! npm -v 1.4.28
       npm ERR! code ELIFECYCLE
       npm ERR!
       npm ERR! Additional logging details can be found in:
       npm ERR!     /tmp/build_3550e8f7-0269-4253-a8cf-f39ff7f9d0fb/npm-debug.log
       npm ERR! not ok code 0

Full trace: https://gist.github.com/jedfoster/9e1e919c46ca1707dd2c

Am I doing it wrong?

[nschonni]

Libsass now requires a C++ compiler that supports C++11. It isn't clear why the build is being forced though as node-sass ships with binaries for 0.10.32.

[Rowno]

I'm getting missing Python errors installing the latest node-sass on Windows 7. Looks like it's trying to build when it shouldn't need to, might be related?

[smashercosmo]

same problem ( build failed on windows 7

[am11]

It seems like it throws exception in one of these three lines: 37, 43 or 45 in build.js. The line 56 (inside catch block) triggers the rebuild.

For the record, I can't reproduce it locally in Win8.1.1 or Ubuntu12 with node v0.10.32.

[am11]

@nschonni to find out what's going wrong on those systems; can we make a debug release with fs.writeFileSync('./node-sass-debug.log', ex.message, 'utf8') to capture the exception at: build.js#L55?

[Subash]

Here you go, console.log(ex)

[am11]

Could you try with node.exe x86-32 bit: http://nodejs.org/download/? First uninstall the exiting node and reinstall 32 bit. If that works, or gives different error, then this is one issue with x64 bit. I can think of few reasons; why it's happening.
If 32-bit throws some other error, please show it as well.

Thanks for diagnosing @Subash! 👍

[Subash]

I guess the 64 bit pre-built binding has problems, I just installed 32 bit node and everything seems to be working fine.

[am11]

I think this is because, when I made the binary for x86-64 bit arch, I used the standalone copy of node.exe which somehow caused this erroneous binary. I think we need to have a separate VM configured for this thing.

But wait! going by this logic^^, there shouldn't be an issue with Linux build; as there I was using 64-bit version as installed and 32-bit as standalone. The log by @jedfoster says that the system wanted 64 bit version and found it. But yet the binary was flawed.

More weirdness to the mix; just installed on Ubuntu x64 VM with node x64, and it worked!

[jedfoster]

I should add that it works just fine on my MacBook Pro. OS X 10.9.5.

[Subash]

Failed on Ubuntu 32 bit as well,

[am11]

The suitable solution would probably come from #56, when the binary building is automated via Vagrant.

For now, the work around is to install python 2.7.8 (with evn variable set) and C++11 compiler (GCC 4.8 or VS2013+ on Windows). The script will rebuild the binaries for your system.

[Subash]

@am11 I don't have 64 bit ubuntu but I will try to contribute 32 bit ubuntu binary,

[Subash]

@am11 How did you generate the bindings ?