The reply beneath is probably going not full to your state of affairs, however will get issues rolling should you take the initiative.
A compiled executable that’s statically linked is 100% full for a selected laptop structure, and are a lot bigger in dimension than dynamically linked executable that are likely to port higher throughout computer systems with various architectures.
Your improperly functioning executables are utilizing dynamically linked libraries as an alternative of utilizing statically linked libraries. Your executable(s) are in search of a dynamically linked library (file) within the /usr/native/decide/miniupnpc/lib/ listing known as miniupnpc.16.dylib.
When you have Homebrew put in, a "% brew checklist" will point out if miniupnpc bundle is put in. A "% brew ls -v miniupnpc" will establish the trail the place are the recordsdata miniupnpc bundle recordsdata are put in such because the dynamically linked lib/libminiupnpc.16.dylib library file or the statically linked lib/libminiupnpc.a library file.
You’ll need to learn in regards to the HOMEBREW_LIBRARY_PATH environmental variable and the DYLD_LIBRARY_PATH environmental variable used on a Mac.
The trail to your command line interface and the *.dmg file are completely different. Use the UNIX "% which bitcoind" or "% which bitcoin-cli" to establish what the command line path actually is about to inside your UNIX shell.
