Rebuilt linux binaries on debian wheezy · sass/node-sass-binaries@9d6417d · GitHub

This repository has been archived by the owner on May 28, 2018. It is now read-only.

Commit

Rebuilt linux binaries on debian wheezy

Browse files

Loading branch information

andrew committed Nov 19, 2014

1 parent cf66775 commit 9d6417d

linux-ia32/binding.node

100644 → 100755

Binary file not shown.

linux-x64/binding.node

100644 → 100755

Binary file not shown.

13 comments on commit `9d6417d`

ixtli commented on `9d6417d` Nov 21, 2014

I think this commit may have broken installation of node-sass@1.2.3 on ubuntu 12 LTE, tough its entirely possible that I've misconfigured something. I've recorded some digging i've done at sass/node-sass#550 . Let me know if I can help in any other way.

I don't know much about what the output of the libsass is supposed to do (is it an executable binary image, or is it an object file ?) so I'm not sure if i should be able to execute it (chmod +x binding.node && ./binding.node) without getting a segfault.

Contributor

am11 commented on `9d6417d` Nov 21, 2014

is it an executable binary image, or is it an object file

Not an object, binding.node is a compiled dynamic / shared binary lib.

ixtli commented on `9d6417d` Nov 21, 2014

Ok, that's kinda what I thought. this line in node-sass calls require on node-sass/vendor/linux-x64/binding.node on my ubuntu box but for some their build script (scripts/build.js) is failing like this:

module.js:355
  Module._extensions[extension](this, filename);
                               ^
Error: Module did not self-register.

folknor commented on `9d6417d` Nov 22, 2014

Same problem for me on Ubuntu 15.04 with npm 2.1.6 and node 0.11.14.

Contributor Author

andrew commented on `9d6417d` Nov 22, 2014

It should be noted that node-sass doesn't support v0.11.x yet

folknor commented on `9d6417d` Nov 22, 2014

How can you tell that it doesn't? I can't find that written anywhere, and package.json says "node": ">=0.10.0".

Contributor

am11 commented on `9d6417d` Nov 22, 2014

@vhaarr, because the dependencies we are using have issues with v0.11.x. It isn't stable for 0.11 yet.

ixtli commented on `9d6417d` Nov 22, 2014 via email

His point remains: this was not noted anywhere.

On Sat, Nov 22, 2014 at 07:16 Adeel Mujahid ***@***.*** wrote: @vhaarr https://github.com/vhaarr, because the dependencies we are using have issues with v0.11.x. It isn't stable for 0.11 yet. — Reply to this email directly or view it on GitHub 9d6417d#commitcomment-8683825 .

Member

kevva commented on `9d6417d` Nov 22, 2014

Don't expect everything to work with an unstable version of node.

folknor commented on `9d6417d` Nov 22, 2014

Whomever told you I had any expectations is mistaken. I do not expect anything from free software.

That doesn't mean practices in this project don't need work - this sort of fact could be noted somewhere, some place, in some form. Not that my opinion has any merit or sway or deserves to be listened to.

But, now it is noted, I guess. Here.

ixtli commented on `9d6417d` Nov 22, 2014 via email

Yes, I think it was a jump to say any of us were "expecting" things to work with "unstable" builds. We're participating in free software development by documenting issues. If it came across that I was upset or entitled in some way then sorry, but noting breakage is the purpose of github issues. I think it's important that, for most developers, installing NVM and then selecting the most recent version of node is common practice. It's difficult for someone new to know to use a 10x version versus an 11x version so there are probably many more people in the same situation. It's also important that node-sass worked with the current stable version of 11 at 1.2.2 as far as I can tell.

On Sat Nov 22 2014 at 2:11:49 PM Vidar Haarr ***@***.*** wrote: Whomever told you I had any expectations is mistaken. I do not expect anything from free software. That doesn't mean practices in this project don't need work - this sort of fact could be noted somewhere, some place, in some form. Not that my opinion has any merit or sway or deserves to be listened to. But, now it is noted, I guess. Here. — Reply to this email directly or view it on GitHub 9d6417d#commitcomment-8684964 .

Member

kevva commented on `9d6417d` Nov 22, 2014

Documenting that it doesn't work on an unstable version of node? Why? Thank you for reporting it though :)!

Contributor

am11 commented on `9d6417d` Nov 22, 2014

BTW, the current stable version of nodejs is: v0.10.33.
Source: http://nodejs.org/.

Please sign in to comment.