Categories
- 1.6K All Categories
- 1.4K General
- 278 FabulousPanda Apps
- 57 Uke Ukulele Tuner
- 38 Unlimited Colouring Art
- 92 De Stijl Art Factory
- 45 Wheres the Unicorn and Meerkat
- 56 XMR Monero and Aeon mining
- 33 Pools
- 55 FPGA and ASIC devices
- 29 cgminer for Mac OS X
- 44 bfgminer for Mac OS X
- 286 Support
- 48 Feature Requests
Buy Monero at local Monero
Trade BTC for Monero at AgoraDesk
Use Anonymous Ads
Use Anonymous Ads
Error running xmr-stak-cpu on OS 10.10.5
Hi
I'm not sure what I'm doing wrong but I get this error when running xmr-stak-cpu
dyld: lazy symbol binding failed: Symbol not found: _clock_gettime
Referenced from: /Applications/xmr-stak-cpu-macOS/./libmicrohttpd/lib/libmicrohttpd.12.dylib
Expected in: /usr/lib/libSystem.B.dylib
dyld: Symbol not found: _clock_gettime
Referenced from: /Applications/xmr-stak-cpu-macOS/./libmicrohttpd/lib/libmicrohttpd.12.dylib
Expected in: /usr/lib/libSystem.B.dylib
Trace/BPT trap: 5
Any help would be appreciated
Cheers
Comments
clock_gettime is not defined in older versions of macOS so that's causing the issue here, you can compile the miner without libmicrohttpd though and it should work for you.
@FabulousPanda I am having same issue in 10.11.6 - How do I compile the miner without that? I don't see any option in the config... thank you!
Compiling is what you do to build the code from the repo which has been replaced by this one now:
https://github.com/fireice-uk/xmr-stak/
I compiled that for CPU which is on the downloads page without httpd so it should work on 10.11
i get more or less the same error but for config.txt dont found!what can i do?
thank you
i get more or less the same error but for config.txt dont found!what can i do?
thank you
''''''
Failed to open config file config.txt.
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
'''''''
That might mean there's no config.txt in the same folder as the miner binary but I think it also happens if you double click the binary instead of running it on the command line.
it is in the same folder as zip provided!i did the double click but i also run it on the command line!any other ideas?
If you double click and then run from the command line the Terminal instance retains something of the previous instance which caused it to fail, so open a new Terminal window and run it fresh exactly as per the instructions included in the downloads I provide. It's a bit sensitive.