Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

Node sass fails to install (io.js 3.0.0 / osx) #1086

Closed
teeli opened this issue Aug 19, 2015 · 26 comments
Closed

Node sass fails to install (io.js 3.0.0 / osx) #1086

teeli opened this issue Aug 19, 2015 · 26 comments

Comments

@teeli
Copy link

teeli commented Aug 19, 2015

node-sass seems to throw a bunch or node-gyp errors while installing on io.js 3.0.0 on osx.

I see multiple errors like:
/Users/teel/.node-gyp/3.0.0/deps/v8/include/v8.h:221:5: error: assigning to 'v8::Function *volatile' from incompatible type 'v8::Value *'

4 warnings and 10 errors generated.
make: *** [Release/obj.target/binding/src/binding.o] Error 1
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/Users/teel/Projects/redacted/node_modules/node-sass/node_modules/pangyp/lib/build.js:271:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Darwin 14.4.0
gyp ERR! command "/usr/local/bin/iojs" "/Users/teel/Projects/redacted/node_modules/node-sass/node_modules/pangyp/bin/node-gyp" "rebuild" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /Users/teel/Projects/redacted/node_modules/node-sass
gyp ERR! node -v v3.0.0
gyp ERR! pangyp -v v2.3.0
gyp ERR! not ok 
Build failed
npm ERR! Darwin 14.4.0
npm ERR! argv "/usr/local/bin/iojs" "/usr/local/bin/npm" "install" "sass-loader"
npm ERR! node v3.0.0
npm ERR! npm  v2.13.5
npm ERR! code ELIFECYCLE

npm ERR! node-sass@3.2.0 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the node-sass@3.2.0 postinstall script 'node scripts/build.js'.
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 scripts/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! Please include the following file with any support request:
npm ERR!     /Users/teel/Projects/redacted/npm-debug.log
@AbrahamAlcaina
Copy link

I have the same issue

> node-sass@3.2.0 install /Users/abraham/Documents/Git/isomorphic-flux/node_modules/node-sass
> node scripts/install.js

Cannot download "https://github.com/sass/node-sass/releases/download/v3.2.0/darwin-x64-45_binding.node": HTTP error 404 Not Found

> node-sass@3.2.0 postinstall /Users/abraham/Documents/Git/isomorphic-flux/node_modules/node-sass
> node scripts/build.js

Building: /Users/abraham/.nvm/versions/io.js/v3.0.0/bin/iojs node_modules/pangyp/bin/node-gyp rebuild --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
gyp: /Users/abraham/.node-gyp/3.0.0/common.gypi not found (cwd: /Users/abraham/Documents/Git/isomorphic-flux/node_modules/node-sass) while reading includes of binding.gyp while trying to load binding.gyp
gyp ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/Users/abraham/Documents/Git/isomorphic-flux/node_modules/node-sass/node_modules/pangyp/lib/configure.js:345:16)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Darwin 14.5.0
gyp ERR! command "/Users/abraham/.nvm/versions/io.js/v3.0.0/bin/iojs" "/Users/abraham/Documents/Git/isomorphic-flux/node_modules/node-sass/node_modules/pangyp/bin/node-gyp" "rebuild" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /Users/abraham/Documents/Git/isomorphic-flux/node_modules/node-sass
gyp ERR! node -v v3.0.0
gyp ERR! pangyp -v v2.3.0
gyp ERR! not ok 
Build failed
npm ERR! Darwin 14.5.0
npm ERR! argv "/Users/abraham/.nvm/versions/io.js/v3.0.0/bin/iojs" "/Users/abraham/.nvm/versions/io.js/v3.0.0/bin/npm" "install"
npm ERR! node v3.0.0
npm ERR! npm  v2.13.3
npm ERR! code ELIFECYCLE

npm ERR! node-sass@3.2.0 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the node-sass@3.2.0 postinstall script 'node scripts/build.js'.
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 scripts/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! Please include the following file with any support request:
npm ERR!     /Users/abraham/Documents/Git/isomorphic-flux/npm-debug.log

@pheebcodes
Copy link

Same error. Ubuntu 15.04, io.js 3.1.0

https://gist.github.com/chncdcksn/f72d62d7ad13a400312a

@dhritzkiv
Copy link

Ditto. OS X 10.10; io.js 3.1.0; node-gyp 3.1.0

@saper
Copy link
Member

saper commented Aug 20, 2015

This is #1053, currently fixed in git master and under testing for a release.

@ai
Copy link

ai commented Aug 23, 2015

Same problem in PostCSS benchmark.

@saper
Copy link
Member

saper commented Aug 23, 2015 via email

@ai
Copy link

ai commented Aug 23, 2015

@saper latest node-sass still falls :)

@saper
Copy link
Member

saper commented Aug 23, 2015 via email

@jbardrof
Copy link

It still appears to be failing:

npm install git+https://git@github.com/sass/node-sass.git

Cannot download "https://github.com/sass/node-sass/releases/download/v3.2.0/linux-x64-45_binding.node": HTTP error 404 Not Found

@saper
Copy link
Member

saper commented Aug 24, 2015

This is because #1054 is not released yet.

@mansona
Copy link

mansona commented Aug 25, 2015

Is there an ETA on that release?

@xzyfer
Copy link
Contributor

xzyfer commented Aug 25, 2015

This will likely ship in the AM AEST (approx 14hrs.).

@frankleng
Copy link

+1 to get updates. thanks

@mansona
Copy link

mansona commented Aug 25, 2015

@xzyfer thanks for the update, I look forward to the release 👍

@mgol mgol mentioned this issue Aug 25, 2015
@xzyfer xzyfer modified the milestones: next.minor, v3.3.0 Aug 26, 2015
@xzyfer
Copy link
Contributor

xzyfer commented Aug 26, 2015

v3.3.0 has been released

@xzyfer xzyfer closed this as completed Aug 26, 2015
@xzyfer
Copy link
Contributor

xzyfer commented Aug 26, 2015

Reopening this because we've had to pull the v3.3.x release due a segfault issue when used with fsevent (#1107).

@xzyfer xzyfer reopened this Aug 26, 2015
@xzyfer
Copy link
Contributor

xzyfer commented Aug 26, 2015

If you desperately need iojs v3 support you can use the beta tag, but we caution against this.

npm install node-sass@beta

@jalcine
Copy link

jalcine commented Aug 26, 2015

@xzyfer commented on Aug 26, 2015, 9:58 AM EDT:

If you desperately need iojs v3 support you can use the beta tag, but we caution against this.

npm install node-sass@beta

So far, I haven't run into any issues; but I'll be sure to report them (I'm using this via broccoli).

@puzrin
Copy link

puzrin commented Aug 26, 2015

@xzyfer any info when 3.3.1+ will be available in npm as stable (not as node-sass@beta)?

@saper
Copy link
Member

saper commented Aug 26, 2015

We need to check why fsevents/fsevents#82 occurs in conjunction with node-sass 3.3.0

@xzyfer
Copy link
Contributor

xzyfer commented Aug 27, 2015

@puzrin there's not estimate yet. We're having an incompatiblity with fsevents which is widely used and core to projects like gulp and webpack. Until this is resolved we cannot ship iojs v3 compatibility.

Subscribe to #1107 and fsevents/fsevents#82 for updates on the situation.

@puzrin
Copy link

puzrin commented Aug 27, 2015

No prob. I have broken travis tests in mincer and wished to understand, should i disable iojs env or wait a bit. If fsevent is the only blocker, there is a good probability of improvement in near future.

@xzyfer
Copy link
Contributor

xzyfer commented Aug 27, 2015

Yes, we're purely blocked on fsevents at the moment.

You can enable iojs for specific versions in travis like do https://github.com/sass/node-sass/blob/master/.travis.yml#L7-L13

Just remove iojs-v3 and you should be fine to use Node Sass.

@markogresak
Copy link

Please note that installing @beta will throw segfault even in node v0.12.7, happened to me after switching from v3.0.0 (also segfaulted). It happened in a project where I was using sass-loader.

@xzyfer
Copy link
Contributor

xzyfer commented Aug 31, 2015

Fixed in v3.3.2.

@xzyfer xzyfer closed this as completed Aug 31, 2015
@xzyfer xzyfer modified the milestones: v3.3.2, v3.3.0 Aug 31, 2015
bryk added a commit to kubernetes/dashboard that referenced this issue Nov 9, 2015
There was an issue with the package that prevented it from compilation on OSX, see: sass/node-sass#1086
@boiawang
Copy link

update gcc(4.6+).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests