-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Segmentation fault: 11 #20
Comments
hm, could you provide more info please? "it works for me" 32/64bit, what os, node version, etc. |
Well i'm trying it in node 0.8.5 on OS X Lion (64bit) node-sass version is latest from npm as of tonight |
Ok, I fixed this issue. If you're impatient, you can git clone and build it, or wait for andrew to push another version to the main npm repository. The main issue was that it targets macosx 10.7 -- hopefully this doesn't cause issues for people running older macosx versions. ping @andrew : please publish a new version of this library. |
I briefly blogged about this, should anyone else have issues getting their node extensions to work properly in lion: http://www.deanmao.com/2012/08/23/node-native-extensions-in-mountain-lion/ |
@deanmao I've pushed 0.2.3 to npm, cheers! |
I can just confirm that this update does not break on older macosx - tested on Snow Leopard 10.6.8 with node 0.8.5 |
I was have this error when I was trying to use |
Same error here when using an undefined variable like |
@MariusRumpf, if you have installed via If you are compiling and installing current master, then its weird because we have couple of test cases for it and all are passing. If that's the latter case, please expand on what command you are using? |
@am11 Installed it with |
Hey, I am getting this error on the .render() api method.
I noticed some people are having this issue on for grunt-sass as well:
sindresorhus/grunt-sass#2
I am testing with really simple code with no errors:
var str = "#main
{
.more
{
}
}"
//
sass.render(str, function (err, data) { // Segmentation fault 11 } );
The text was updated successfully, but these errors were encountered: