Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Sodium Native Error on Mac OSX

See original GitHub issue

I am reporting:

Bug Report

Please give us details about your installation to assist you. Run dat -v to see the version of Dat you are using.

Operating system: Mac OS 10.8.5
Node Version: v10.15.3
Dat Version: dat@13.13.0

Expected behavior

Actual behavior

Running dat share ne generates errors:

→ dat share ne
dyld: lazy symbol binding failed: Symbol not found: _memset_s
  Referenced from: /Users/dmitrizaitsev/.npm-global/lib/node_modules/dat/node_modules/sodium-native/prebuilds/darwin-x64/libsodium.dylib
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _memset_s
  Referenced from: /Users/dmitrizaitsev/.npm-global/lib/node_modules/dat/node_modules/sodium-native/prebuilds/darwin-x64/libsodium.dylib
  Expected in: /usr/lib/libSystem.B.dylib

Trace/BPT trap: 5

Debug Logs

→ DEBUG=dat* dat share ne
  dat Dat DEBUG mode engaged, enabling quiet mode +0ms
  dat dat 13.13.0 +7ms
  dat node v10.15.3 +0ms
  dat Sharing archive { _: [ 'ne' ],
  utp: true,
  debug: false,
  quiet: true,
  sparse: false,
  import: true,
  ignoreHidden: true,
  'ignore-hidden': true,
  watch: true,
  logspeed: 400,
  dir: 'ne' } +0ms
dyld: lazy symbol binding failed: Symbol not found: _memset_s
  Referenced from: /Users/dmitrizaitsev/.npm-global/lib/node_modules/dat/node_modules/sodium-native/prebuilds/darwin-x64/libsodium.dylib
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _memset_s
  Referenced from: /Users/dmitrizaitsev/.npm-global/lib/node_modules/dat/node_modules/sodium-native/prebuilds/darwin-x64/libsodium.dylib
  Expected in: /usr/lib/libSystem.B.dylib

Trace/BPT trap: 5

Issue Analytics

State:
Created 4 years ago
Comments:16 (1 by maintainers)

Top GitHub Comments

2reactions

emilbayescommented, May 17, 2019

@dmitriz It’s not as much about Apple as it is an update to your standard library. It may be possible to do on your own without upgrading the OS, but I don’t know how. Sometimes you also have to assume so basic level of support 😃 The function in question is a secure way to wipe sensitive material and we can’t support systems that don’t have it. memset_s was introduced with the C11 standard

1reaction

emilbayescommented, Aug 9, 2019

Everything is back to normal now. https://github.com/sodium-friends/sodium-native-citgm

Top Results From Across the Web

Sodium Native Error on Mac OSX · Issue #1110 - GitHub

Run dat -v to see the version of Dat you are using. Operating system: Mac OS 10.8.5; Node Version: v10.15.3; Dat Version: dat@13.13.0 ......

sodium-native - npm

Start using sodium-native in your project by running `npm i sodium-native`. There are 188 other projects in the npm registry using ...

Can't install node-sodium on Windows - Stack Overflow

I chose Sodium as the encryption package, but I'm having difficulties when it comes to installing it. I tried setting my VS version...

How to Contribute - Blitz.js

(Optional, macOS only) Install required packages for sodium-native. If you spot any issues related to sodium-native , run the following command to fix...

How to fix EACCES errors with NPM on MacOS - WILL & SKILL

There are times when You get an ugly EACCES error message from NPM when You try to install an ... Faisals-Mac:Code faisal$ npm...