-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Can't install on Window 7 #184
Comments
Can you post the prebuild check? It should only trigger the build if the binary testing failed. PS: 0.8.9 is pretty "old" now and there have been security releases to the 0.8 node branch |
I just installed [email protected] using node v.0.10.20 on Windows 7 64bit. Everything seems fine, even "npm test node-sass". |
I am wondering if this issue has something to do with the npm issue that was happening at the time this issue was logged... |
@nschonni This dropped of my radar until @k-j-kleist and @LaurentGoderre just commented. I'm not sure why that log show's node v0.8.9 as the version because I have v0.10.22 installed. I use nodist to manage my versions of node, so it's possible that there is an issue caused by that not upgrading node-gyp properly when upgrading the version of node? I was able to get node-sass to successfully install using the --force flag with the npm install. It appears to be working fine in the project I have been working on. However, without using --force it still fails to build on the install. Here is the full log. Had to separate into two comments below because of github character restrictions. |
|
std::string &,size_t,Sass::Backtrace *)' being compiled npm ERR! System Windows_NT 6.1.7601
|
Unless you REALLY need to do it like this, I would suggest only installing this through npm. Building it on Windows is a real pain. |
@LaurentGoderre I am installing node-sass with npm. This build happens as part of the install. |
@devert: Laurent and I just had a similar discussion in a different thread. To be really clear, which option are you doing: A) In the directory of some project where you want to use node-sass, run "npm install node-sass" OR (A) is what @LaurentGoderre is suggesting. (B) is really hard on Windows. |
@TomGault I'm doing option (A). As I mentioned, I can successfully install the module in my project if I run the following.
|
@devert, okay, thanks for clarifying! |
That's weird, this is what I get
|
@devert do you have multiple Visual Studio installs on your machine? |
For reference, I have VS 2008, 2012 and 2013 installed and set up for C++ development and had no problems installing. (I haven't intentionally done anything with gyp though). |
It could be the missing Windows SDK too |
Hi, I was trying to install on Ubuntu 12.04 and this is the string of messages that I got. Can you help?
gyp ERR! configure error npm ERR! System Linux 3.2.0-57-generic |
@kalimati when did this occur? |
while installing with the command |
What do you get if you run
|
@kalimati please file a new issue as this is to do with building on Windows. As described in the log, node-gyp doesn't support pre release builds of node. |
I seem to have trouble installing it on Windows 7 too, although I'm getting a different error. I am also using option (A) as @TomGault described.
|
I'm having same problem with npm install. It seems to conflict with some Visual Studio files, but I have uninstalled Visual Studio year ago. But everyone know it is almost impossible to totally uninstall Visual Studio... Is there a way to install without dependencies to visual studio? |
Are you installing from npm directly or cloning locally and then installing from source? |
npm directly... But problem is solved, I uninstalled about everything, including node.js, reinstalling helped. I don't know why... |
I just created a test project and ran |
You shouldn't need to use force but let's address this in the otrher issue is that ok with you? |
Yep. That's fine. What I was describing is that I don't need to use force anymore. That was what I originally needed to do to get it working. So all looks good. |
Oh nice! You shouldn't need Visual Studio anymore. |
I wish ;) Unfortunately I have to work with .NET developers. |
Lol! They are not all that bad, I hope (I used to be one of them ;) ) |
Added missing parenthesis to README.md
Improve const-correctness in sass_interface.h
I get the following build error when trying to install node-sass
The text was updated successfully, but these errors were encountered: