Closed Chailotl closed 6 years ago
https://bitcointalk.org/index.php?topic=304389.0
How is your VPS for memory? You might have luck compiling the libraries on a similar (same architecture, same OS version or at the very least the same library versions, including glibc) Linux box with node-gyp and then copying the binaries.
If I recall correctly the VPS has 512 megabytes of RAM. Is that not enough?
I was on mobile and had missed the link you sent, and sweet mother of mercy it worked! A thousand thanks Rantanen!
Oh my goodness, it fixed every other bizarre npm install issue I had too, many thanks!
This is NOT on Windows, that's a path I wish I never went down. This is on a fresh install of a Debian-based Linux x64 installation on a VPS from DigitalOcean.
What should happen:
What actually happens: (exaggeration)
Click to expand for full logs
``` root@server:~/Mikolai# npm install node-opus > ref@1.3.5 install /root/Mikolai/node_modules/ref > node-gyp rebuild make: Entering directory '/root/Mikolai/node_modules/ref/build' CXX(target) Release/obj.target/binding/src/binding.o g++: internal compiler error: Killed (program cc1plus) Please submit a full bug report, with preprocessed source if appropriate. SeeYes, I have
build-essentials
,auto-conf
,libtool
, as well asnode-gyp
, I had enough headaches with half installed software.I've also pulled the git repository and manually built it with
./configure --enable-static --disable-shared --with-pic
and thenmake
, and dragged it to the node_modules folder, but that cropped up another issue about missing bindings, so I then triednode-gyp rebuild
, which starts up and requires the module without a hitch, but when it came to using the module it crashes without an error log.God have mercy on my tortured soul.