The reply beneath is probably going not full on your scenario, however will get issues rolling when you take the initiative.
A compiled executable that’s statically linked is 100% full for a specific 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 searching for a dynamically linked library (file) within the /usr/native/decide/miniupnpc/lib/ listing referred to as miniupnpc.16.dylib.
When you have Homebrew put in, a "% brew record" will point out if miniupnpc bundle is put in. A "% brew ls -v miniupnpc" will determine the trail the place are the information miniupnpc bundle information are put in such because the dynamically linked lib/libminiupnpc.16.dylib library file or the statically linked lib/libminiupnpc.a library file.
You will have to learn in regards to the HOMEBREW_LIBRARY_PATH environmental variable and the DYLD_LIBRARY_PATH environmental variable used on a Mac.
The trail on your command line interface and the *.dmg file are totally different. Use the UNIX "% which bitcoind" or "% which bitcoin-cli" to determine what the command line path actually is about to inside your UNIX shell.