-
Notifications
You must be signed in to change notification settings - Fork 1.3k
random_device: rdrand failed #3047
Comments
This comment has been minimized.
This comment has been minimized.
thing is i ve used it successfully on 2 other machines, both running ubuntu 20.04, the only difference being that those were intel machines, as opposed to this one which is and amd ryzen 7 with b550 chipset; could it be an issues with the linux drivers for this kind of setup? |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@fk1blow looks an incompatibility between the system libraries the binaries are compiled with and those on your local machine. Could be something about the architecture of that machine or an ABI mismatch. Unfortunately there isn't much we can do. Out of curiosity does node-sass@^4 install without issue? |
This comment has been minimized.
This comment has been minimized.
@xzyfer tried it and it fails in the same way. Thanks for your help! |
@fk1blow can't say for sure sorry |
It is unlikely node-sass can do anything to make it work :( |
Probably caused by sass/libsass#3151 |
For what it's worth, I experienced this "RDRAND failed" error after upgrading from Debian10 to Debian11 when running "yarn add node-sass" in an empty directory. (Apparently Debian11 brings a newer libstdc++ which perhaps has a newer implementation of the C++ std::random_device class that started using RDRAND?) I resolved the issue by upgrading the BIOS. (CPU: AMD Ryzen 7 5800X, Motherboard: GIGABYTE B550I AORUS PRO AX. Original BIOS was version "F3" which triggered the RDRAND errors, updating to BIOS version "F13" resolved the issue.) |
node version: v10.19.0
os: ubuntu 20.04
npm version: 6.14.8
Node platform: linux
Node process:
Node architecture: x64
got this when doing a
npm i
which requires"node-sass": "^4.12.0"
The text was updated successfully, but these errors were encountered: