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
Installation Failing (on Linux, Windows or Heroku etc.) #467
Comments
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. |
I'm getting missing Python errors installing the latest |
same problem ( build failed on windows 7 |
@nschonni to find out what's going wrong on those systems; can we make a debug release with |
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. Thanks for diagnosing @Subash! 👍 |
I guess the 64 bit pre-built binding has problems, I just installed 32 bit node and everything seems to be working fine. |
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! |
I should add that it works just fine on my MacBook Pro. OS X 10.9.5. |
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. |
@am11 I don't have 64 bit ubuntu but I will try to contribute 32 bit ubuntu binary, |
@am11 How did you generate the bindings ? |
@Subash, that would be awesome! The repository is located here https://github.com/sass/node-sass-binaries: First, fork both repos: README has it, but here is how I do it: Linux: # given you have GCC 4.8 installed
# (see https://github.com/sass/node-sass/blob/master/.travis.yml for installation commands),
# After that:
git clone --recursive https://github.com/subash/node-sass/
git remote add node-sass https://github.com/sass/node-sass/
git clone https://github.com/subash/node-sass-binaries/
git remote add node-sass-binaries https://github.com/sass/node-sass-binaries/
cd node-sass
git submodule update --init --recursive
npm install
npm install -g node-gyp
rm -r build/; rm -r bin/linux-ia32-v8-3.14; rm -r bin/linux-x64-v8-3.14
node build
# test it
npm test
# copy the bin/linux* folder and replace to its conterpart in node-sass-binaries, then
git add .
git commit -am "Linux: Binaries updated for (x86-32)." # or 64
git push
# then make a PR on node-sass-binaries repository. Windows (using PowerShell, the one with SSH and Git support; that comes with http://windows.github.com/): # given you have VS2013 Update 3 (Pro or Express for desktop) installed
# then fork both repos; node-sass and node-sass-binaries.
# After that:
git clone --recursive https://github.com/subash/node-sass/
git remote add node-sass https://github.com/sass/node-sass/
git clone https://github.com/subash/node-sass-binaries/
git remote add node-sass-binaries https://github.com/sass/node-sass-binaries/
cd node-sass
git submodule update --init --recursive
npm install
npm install -g node-gyp
rm -r build/; rm -r bin/win32-ia32-v8-3.14; rm -r bin/windows-x64-v8-3.14
node build
# test it
npm test
# copy the bin/linux* folder and replace to its conterpart in node-sass-binaries, then
git add .
git commit -am "Windows: Binaries updated for (x86-32)." # or 64
git push
# then make a PR on node-sass-binaries repository |
Built on one machine, failed to run on another. There is something really wrong with our build system (the compiler switches and all). This issue is recurring since 2012: #13. |
Same issue here... 10927 info install node-sass@1.0.0 |
Interestingly, my node-sass app builds and runs on a Digital Ocean droplet. Ubuntu 14.04 x64 vmlinuz-3.13.0-24-generic, deployed with Dokku. |
I just uninstalled NodeJS x64 and downloaded+installed the 32 bit version. Must be a issue with the x64 version of NodeJS |
^ same. will compile times decrease further using x64 once the build errors get resolved? i'm under the impression they will, but don't know/understand 100% |
👍 having same issue with Heroku |
This just stopped me from deploying to heroku:
As far as I understand it, the suggested workaround is not possible on Heroku? |
same problem here, trying to install gulp-sass on drone.io: https://travis-ci.org/globocom/clappr/builds/39981423 |
Guys, we are tracking this issue at #497. Nonetheless, the actual solution would be something like #56. @kevinansfield, that's right. The workaround wouldn't work for heorku as is. You can, however, build on *nix-x64 with node-x64 and restore the package manually (remove it as dependency). After cloning repo: |
We have a solution (for Heroku) :) Heroku released a new, up to date stack today: https://blog.heroku.com/archives/2014/11/4/cedar_14_now_generally_available This stack has the necessary libs for the building of Migrate your ember-cli-heroku-app / create a new one on this stack and the push should succeed! |
I have a fix for Travis too, updating g++ like explained here. |
I'm running on the latest
|
|
I've tried a few different version but on Heroku it ignores the specified npm version and uses the version packaged with node. I'm using version |
Can you share part of your |
So it seems like issue may be related to the npm version. Unfortunately on heroku you can't specify a npm version. It uses the version that is packaged with node. I was able to create a custom buildpack that updates the latest npm https://github.com/micahlmartin/heroku-buildpack-nodejs. Here's the app I'm trying to deploy: https://github.com/micahlmartin/nuts. I was able to get it to work in this case. |
fyi there is a branch which uses the latest npm called |
Getting this on OSX Yosemite.
|
EDIT: Migrating to Cedar-14 stack on Heroku solved this problem. I'm trying to switch to node-sass from Ruby version and got the following error while trying to deploy it to Heroku with their new Node buildpack (https://github.com/heroku/heroku-buildpack-nodejs/tree/yoga) with npm 2.1.16:
Is it something that's possible to fix on my end or is it an issue with Heroku? |
For anyone still having issues, upgrading to version |
2.0.0-beta works! |
2.0.0-beta works on Yosemite. Thanks micahlmartin. |
@rualatngua 2.0.1 stable is out. |
This issue is back on 2.0.1(node 0.10.36). I had to manually install 2.0.0-beta to get this installed on Ubuntu. |
Hi, I have problems too. I tried the following versions : This config works on my host machine (windows 8.1) but I get the following error on my ubuntu 14.04 VM : I manage to make this works on the ubuntu VM with the following versions : Hope this helps! |
@trompx you are using obsolete versions of node-sass - besides if you share a directory between two platforms (operating systems) you need have two binaries installed so do |
@saper I believe |
Error:
Full trace: https://gist.github.com/jedfoster/9e1e919c46ca1707dd2c
Am I doing it wrong?
The text was updated successfully, but these errors were encountered: