4.7.0-4.7.2 binaries incompatible with CentOS 5 - ELF file OS ABI invalid

[ReidBraswell]

Before opening an issue:

• Check that the version of node-sass you're trying to install supports your version of Node by looking at the release page for that version https://github.com/sass/node-sass/releases
• Read the common workarounds in the TROUBLESHOOTING.md
• Search for duplicate or closed issues
• Validate that it runs with both Ruby Sass and LibSass
• Prepare a reduced test case for any bugs
• Read the contributing guidelines

When reporting an bug, you must provide this information:

• NPM version (npm -v): 3.10.8
• Node version (node -v): 6.9.1
• Node Process (node -p process.versions):
• Node Platform (node -p process.platform): linux
• Node architecture (node -p process.arch): x64
• node-sass version (node -p "require('node-sass').info"): 4.7.1
• npm node-sass versions (npm ls node-sass):

When encountering a syntax, or compilation issue:

• Open an issue on LibSass. You
  may link it back here, but any change will be required there, not here

If you delete this text without following it, your issue will be closed.

Below is the output from our Jenkins job:

npm info lifecycle node-sass@4.7.1~postinstall: node-sass@4.7.1

> node-sass@4.7.1 postinstall /usr/local/jee/hudson/jobs/workspace/front-end/node_modules/node-sass
> node scripts/build.js

Binary found at /usr/local/jee/hudson/jobs/workspace/front-end/node_modules/node-sass/vendor/linux-x64-48/binding.node
Testing binary
Binary has a problem: Error: /usr/local/jee/hudson/jobs/workspace/front-end/node_modules/node-sass/vendor/linux-x64-48/binding.node: ELF file OS ABI invalid
    at Error (native)
    at Object.Module._extensions..node (module.js:597:18)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at module.exports (/usr/local/jee/hudson/jobs/workspace/front-end/node_modules/node-sass/lib/binding.js:19:10)
    at Object.<anonymous> (/usr/local/jee/hudson/jobs/workspace/front-end/node_modules/node-sass/lib/index.js:14:35)
    at Module._compile (module.js:570:32)

On Friday, November 17, we ran a build with node-sass@4.6.1 and did not have any issues.

[xzyfer]

Interesting. Out of curiosity, which OS is this?

We are facing the same exact issue. Our OS is Red Hat Enterprise Linux Server release 5.11 (Tikanga)

We have switched back to 4.6.1 till this issue is fixed.

[xzyfer]

Locking to node-sass@~4.6 will likely work around the issue. Does the issue persist in 4.7.2?

…

On 21 Nov. 2017 8:50 am, "aseem001" ***@***.***> wrote: We are facing the same exact issue. Our OS is Red Hat Enterprise Linux Server release 5.11 (Tikanga) Is there a way around it, like reverting back to 4.6.1? We also did not see this issue when we ran a build with ***@***.*** on Friday, November 17 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2159 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAjZWBk7veEApYSgbsdAnEQggWc0jjDXks5s4fQmgaJpZM4QkvU9> .

[thilo-cts]

We are facing the same issue in Red Hat 5.11(Tikanga). Can you please provide a quick solution.Since I can't switch back to older versions of node-sass as it is referring from ember-cli-sass

[thilo-cts]

@xzyfer Still we are facing the same issue in 4.7.2.

[xzyfer]

We don't understand the problem yet. For now you can add node-sass@4.6.1 in your package.json. npm will install that version even if it's a dependency of another package

…

On 21 Nov. 2017 8:35 pm, "Thilagavathi Indrajit" ***@***.***> wrote: @xzyfer <https://github.com/xzyfer> Still we are facing the same issue in 4.7.2. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2159 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAjZWGayEv0M_qSC7myZPsIGnhz9njstks5s4pl-gaJpZM4QkvU9> .

[thilo-cts]

@xzyfer Yes. We have done the same now. it is working.

[nschonni]

@xzyfer did you rebuild with the old CentOS 5 machine for the linux binaries? I believe this might be because of the really old libc issues we ran into before

[xzyfer]

We've been using CentOS 6 for a while now. I think some of the RPM may have been updated on use though. I had some troubled with the x86 binaries.

[nschonni]

OK, related nodejs/build#898 CentOS/RHEL 5 is only valid for Node < 8 since it's EOL, but I guess it should still be working with 6

[xzyfer]

@stefanpenner are you able to confirm this with your CentOS setup?

[cedricroijakkers]

I can reproduce this issue on the following setup:

RedHat EL 5.9
Node v6.11.2
node-sass versions 4.7.1 and 4.7.2

If you need me to test anything, just let me know. For now, I've rolled back to node-sass 4.6.

[xzyfer]

Are you able to reproduce the issue on a newer version of node? I wonder if it's something specific about node 6

…

On 22 Nov. 2017 7:07 pm, "Cedric Roijakkers" ***@***.***> wrote: I can reproduce this issue on the following setup: RedHat EL 5.9 Node v6.11.2 node-sass versions 4.7.1 and 4.7.2 If you need me to test anything, just let me know. For now, I've rolled back to node-sass 4.6. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2159 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAjZWGtvU-6L0r5iTdcH9B3TE8fxsINnks5s49YngaJpZM4QkvU9> .

[adarBlack]

Hitting this since Sunday. Using node-sass 4.6 now.