Error installing 1.1.4

[gschwartzbard-ra]

I am getting the following error when installing via npm install:

> node-sass@1.1.4 install /jenkins/jobs/webapp.order/workspace/node_modules/gulp-sass/node_modules/node-sass
> node build.js

`linux-x64-v8-3.14` exists; testing
make: Entering directory `/jenkins/jobs/webapp.order/workspace/node_modules/gulp-sass/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 `/jenkins/jobs/webapp.order/workspace/node_modules/gulp-sass/node_modules/node-sass/build'

[fraklo]

I am also having an issue installing

`linux-x64-v8-3.14` exists; testing
make: Entering directory `/pipeline/build/node_modules/gulp-sass/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 `/pipeline/build/node_modules/gulp-sass/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 (/usr/local/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.2.0-54-virtual
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /pipeline/build/node_modules/gulp-sass/node_modules/node-sass
gyp ERR! node -v v0.10.33
gyp ERR! node-gyp -v v1.0.1
gyp ERR! not ok
Build failed

npm ERR! node-sass@1.1.4 install: `node build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass@1.1.4 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.2.0-54-virtual
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! cwd /pipeline/build
npm ERR! node -v v0.10.33
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR! not ok code 0

[Evgenus]

> node-sass@1.1.4 install /home/ubuntu/src/github.com/Evgenus/spa/node_modules/node-sass
> node build.js

`linux-x64-v8-3.14` exists; testing
gyp http GET http://nodejs.org/dist/v0.10.26/node-v0.10.26.tar.gz
gyp http 200 http://nodejs.org/dist/v0.10.26/node-v0.10.26.tar.gz
make: Entering directory `/home/ubuntu/src/github.com/Evgenus/spa/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: Leaving directory `/home/ubuntu/src/github.com/Evgenus/spa/node_modules/node-sass/build'
make: *** [Release/obj.target/binding/binding.o] Error 1
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/home/ubuntu/nvm/v0.10.26/lib/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:797:12)
gyp ERR! System Linux 3.2.0-23-virtual
gyp ERR! command "node" "/home/ubuntu/nvm/v0.10.26/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/ubuntu/src/github.com/Evgenus/spa/node_modules/node-sass
gyp ERR! node -v v0.10.26
gyp ERR! node-gyp -v v0.12.2
gyp ERR! not ok 
Build failed
npm ERR! node-sass@1.1.4 install: `node build.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the node-sass@1.1.4 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.2.0-23-virtual
npm ERR! command "/home/ubuntu/nvm/v0.10.26/bin/node" "/home/ubuntu/nvm/v0.10.26/bin/npm" "install"
npm ERR! cwd /home/ubuntu/src/github.com/Evgenus/spa
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.3
npm ERR! code ELIFECYCLE
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /home/ubuntu/src/github.com/Evgenus/spa/npm-debug.log
npm ERR! not ok code 0

on Windows it eats 6Gb of memory and halts.

[LostSenSS]

In my case installation stops on

node build.js
`win32-x64-v8-3.14` exists; testing

Nothing more. Windows 8.

[am11]

@LostSenSS,

Yes; this is a known issue. See #493 (comment). There is something wrong with the npm install. Even the machine on which I built x64 binary is showing this behavior. If I install it via npm, it hangs. Works fine on x86 Windows machine though.

[fraklo]

My local machine (windows 8.1 64 bit) also hung, but after a good long while i aborted the job and version shows 1.1.4. Everything is running fine. Server however is running what I posted above and fails.

[am11]

Yeah! After seeing your comment, I put installation on x64 Windows laptop. I just turned the monitor on (after like an hour) and it is installed successfully! No rebuilding of binaries, nothing odd happened (except for the delay). I know it's not acceptable, but this is something.. ❕

[mbbender]

same issue here

[bbooth]

Windows 8.1 64 bit as well

> node-sass@1.1.4 install C:\dev\projects\marketplace-ember\node_modules\node-sass
> node build.js

`win32-x64-v8-3.14` exists; testing

It chews up memory until node uses all my available memory (24 Gb) and starts swapping. My HD then goes nuts. Hope this helps troubleshoot.

Update

• Let it run all night and it never came back. Ended up killing the process.
• Work machine installed fine Windows 7 64bit

[flyke]

I have the same problem here on my Win 8 64 bit machine. I have a new project where I'm setting up my Grunt. So I give the command 'npm install'. It installs and downloads everything fine up until node-sass.

Even after 40 minutes, nothing happens after: (replaced actual path with ....... here):

node-sass@1.1.4 install .........\node_modules\grunt-sass\node_modules\node-sass
node build.js

win32-x64-v8-3.14 exists; testing

And also here: node.exe is taking up all my available RAM

Update: it was hard but I was patient and fought the urge to abort the process. After about 50 minutes I got the message:
Binary is fine; exiting

Update 2: The message 'Binary is fine; exiting' was showing for over 1hour and 15minutes. I gave up after that.

I was able to run my sass watcher after this, but as soon as i changed and saved a sass file, and node-sass was supposed to do its work, node.exe immediatly consumed all my RAM. And did not do anything else, so even after waiting a long time, this did not result in any compiled css file. Just a non responsive computer because node.exe uses all the available RAM.

[evoactivity]

Updating GCC to 4.8 fixed this for me.
Running Ubuntu 12.04 server, instructions here if you need them http://askubuntu.com/questions/271388/how-to-install-gcc-4-8

[am11]

Actually, GCC shouldn't be involved. It should use prebuild binaries. Otherwise everybody would have to install Python, C++ compiler and node-gyp in order to install node-sass. The rebuild only occurs, when there is some issue with the existing (prebuild) binary for that system.

[hughlomas]

Same problem on Windows 7 x64

[evoactivity]

@am11 updating GCC was a last resort for me as I didn't think it was building anything from source, but it was the only thing I tried that actually worked. The clues are the lines in the error output which say

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’

[andrew]

I'm not going to have any time to investigate the issue today, to resolve your issue quickly you could pin the version of node-sass to a known working version by adding the following to the dependencies section of your package.json:

"node-sass": "1.0.3"

[aaronwaldon]

Thanks @andrew! I was pulling my hair out, but npm install node-sass@1.0.3 worked for me. :)

[ralabs]

@andrew That workaround will not work since I depend on gulp-sass which depends on node-sass

[fraklo]

@ralabs You can fork gulp-sass and change the dependency (set to 1.0.3). It's what we did for the interim.

Just realized I mentioned the wrong person... sorry @andrew

[aaronwaldon]

@ralabs I'm also using gulp-sass. I cleared out the project's node_modules directory, ran npm install node-sass@1.0.3. Then installed the other gulp plugins from package.json. It worked without hanging or running out of memory. I have both "node-sass": "1.0.3" and "gulp-sass": "^1.2.2" in my package.json dev dependencies. Hope that helps.

[gschwa]

@aaronwaldon I am trying the same right now. Thank you

[aaronwaldon]

@gschwa My pleasure. Did that work?

[am11]

Anyone curious about GCC errors, see our travis.yml for how to update GCC.

For windows, it requires VS2013 Update 3 (pro, ultimate, or express-for-desktop).

[gschwa]

@aaronwaldon Not exactly. I tried putting 1.1.2 (since that version worked) in my package.json but during our Jenkins build it tries to install both 1.1.2 and 1.1.4.

[am11]

Regarding #497 (comment), I think sass/libsass#601 would fix that win-x64 with node-x64 installation delay issue as well. Can't say for sure unless the next release (with latest binaries) is published on npm.

[ethanclevenger91]

Using gulp-sass, I'm no longer having issues. Thanks!

[ocombe]

It works fine on my windows 8.1 x64 now, thanks

[kellyrmilligan]

I am still getting this issue on travis. I have the latest module for gulp-sass and node-sass in my package.json. I tried

   - sudo add-apt-repository -y ppa:ubuntu-toolchain-r/test;
   - sudo apt-get update;
   - sudo apt-get install gcc-4.8 g++-4.8;
   - sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.8 20;
   - sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-4.8 20;
   - sudo g++ --version;
   - sudo apt-get update -qq;

Error: libsass bindings not found. Try reinstalling node-sass?

in my travis.yml file as well. still no luck.

[kellyrmilligan]

as a note, I can get the travis build to pass if I don't check in my node modules, which is slowing my build down. is there any way to make this work with checking in my node modules? guessing I have to dev on the same platform?

[am11]

@kellyrmilligan, can you retry after adding the following to your .travis.yml:

env: 
  SKIP_SASS_BINARY_DOWNLOAD_FOR_CI=true 

[benjipott]

+1

[kellyrmilligan]

working for me at the moment, haven't tried clearing my travis cache of node_modules though. thanks!

[kellyrmilligan]

after clearing the travis cache, it seems teh build will only work if the module is run through npm install from scratch. I'm fine for now, but the first time npm burns me I may need a different solution.

[alfredbez]

I had the same error on my iMac using gulp-sass v1.2.4.

Error: `libsass` bindings not found. Try reinstalling `node-sass`?
    at getBinding (/path/to/my/project/node_modules/gulp-sass/node_modules/node-sass/lib/index.js:21:11)
    at Object.<anonymous> (/path/to/my/project/node_modules/gulp-sass/node_modules/node-sass/lib/index.js:181:23)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/path/to/my/project/node_modules/gulp-sass/index.js:3:17)
    at Module._compile (module.js:456:26)

I switched back to v1.2.3 and it works now.

[odino]

Same issue here. Rollbacking to 1.2.3 "fixed" it for now...scary :)

[ferrybrouwer]

I've just wrote a fix for osx:
https://github.com/ferrybrouwer/node-sass-patch

[ysimonson]

I'm seeing this issue with 2.0.0-beta on mac os x. There's no node-sass/build directory, and the node-sass/vendor directory has a darwin-x64 directory, but it's empty.

[skrobek]

I have te same issue as @ysimonson

[ysimonson]

@skrobek fwiw it seems to build fine on a fresh (newly reformatted) os x install.

[StoneCypher]

This works fine for me, but not for my coworker, as of today using up to date versions. We do not yet know what the difference between our machines is.

We face the same apparent problem as @alfredbez . Hard rolling back to 1.2.3 after torching node_modules did not resolve the problem for us.

My machine is /far/ newer than my coworker's.

[StoneCypher]

@andrew the data seems to suggest that the defect described here is not the defect in the linked ticket, and indeed, that the linked ticket describes more than one unrelated problem.

Are you certain this ticket should be closed?

[izolate]

+1 reopen. Getting Error: libsassbindings not found. Try reinstallingnode-sass?

[am11]

@izolate, this was superseded by #517, which has been resolved. If you are having further problems, please open a new issue with elaborate details like: which versions of npm, nodejs you have installed and which version of node-sass you are trying to install? Also see #635 (comment).

[StoneCypher]

This happens with a fresh install on a mac which never had the tools as of yesterday. I'll gather the actual version numbers for you when that staff member comes in, but for all intents and purposes, it's node-current, npm-current, gulp-current, node-sass current, libsass current.

I'll get you the proper numbers as soon as I am able.

[jclif]

Getting this on a circleci build.

[saper]

@jclif please follow our TROUBLESHOOTING.md guide, and if that does not help please post the result.

This bug pertains node-sass@1.1.4 which is very old and does not support current node engines. We still do not support io.js 3.0 #1053 at the time of writing this.

[waltonryan]

for those that might be having similar issues today, I resolved the problem by upgrading my node-sass-middleware

npm uninstall node-sass-middleware --save //was 0.5.0
npm install node-sass-middleware --save //now 0.9.6

I was facing the issue creating a node app with heroku and keystonejs.