bufferutil: Problem installing on OS X 10.10.5
sudo npm install -g bufferutil
bufferutil@1.2.1 install /usr/local/lib/node_modules/bufferutil node-gyp rebuild
CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
SOLINK_MODULE(target) Release/bufferutil.node
ld: library not found for -lgcc_s.10.5
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [Release/bufferutil.node] Error 1
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:270:23)
gyp ERR! stack at emitTwo (events.js:87:13)
gyp ERR! stack at ChildProcess.emit (events.js:172:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Darwin 14.5.0
gyp ERR! command “/usr/local/bin/node” “/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js” “rebuild”
gyp ERR! cwd /usr/local/lib/node_modules/bufferutil
gyp ERR! node -v v4.1.0
gyp ERR! node-gyp -v v3.0.1
gyp ERR! not ok
npm ERR! Darwin 14.5.0
npm ERR! argv “/usr/local/bin/node” “/usr/local/bin/npm” “install” “-g” “bufferutil”
npm ERR! node v4.1.0
npm ERR! npm v3.3.3
npm ERR! code ELIFECYCLE
npm ERR! bufferutil@1.2.1 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the bufferutil@1.2.1 install script ‘node-gyp rebuild’.
npm ERR! This is most likely a problem with the bufferutil package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls bufferutil
npm ERR! There is likely additional logging output above.
About this issue
- Original URL
- State: closed
- Created 9 years ago
- Comments: 27 (2 by maintainers)
Turns out my issue was unique to OS X 10.10 Xcode. The proper links for -lgcc_s.10.5 are not present. Fixed by: $ cd /usr/local/lib $ sudo ln -s …/…/lib/libSystem.B.dylib libgcc_s.10.5.dylib $ sudo ln -s …/…/lib/libSystem.B.dylib libgcc_s.10.4.dylib
YES! downgrade node@10 to 8 solved the problems. Thanks guys 😃