Late jan 2018 apple/nvidia update broke miner and compilation

[kalamarcito]

Since apple osx security update 2018-001 for osx 10.12.6 (now build 16G1212) and subsequent nvidia driver update, the miner stopped working: it connects to stratum server and receives jobs but does no hash.

Tried to recompile with cli-tools 8.3.2 for xcode 9 (xcode version 9.2 installed), updated 9.0 CUDA toolkit and updated nheqminer-macos version from github. It fails with:

Cuda compilation tools, release 9.0, V9.0.175
Using CUDA 9 Toolkit
Using CUDA 9 compatible 'Command Line Tools for Xcode 8.3.2'
CLONE autoconf
CONFIG autoconf
BUILD autoconf
INSTALL autoconf
make[2]: *** [install] Error 2
make[1]: *** [autoconf_all] Error 2
make: *** [tools_all] Error 2

[cronos45]

https://egpu.io/forums/mac-setup/wip-nvidia-egpu-support-for-high-sierra/

Not really an issue with this code, but here is a link to solve your issue.

[kozyilmaz]

Hi @kalamarcito, as far as I see Nvidia released CUDA Toolkit 9.1 which is compatible with Xcode 9.2 Command Line Tools (latest one). So I tested a working setup on macOS High Sierra (10.13.3) with Xcode 9.2 and CUDA 9.1

[kalamarcito]

Thanks kozyilmaz, I guess I face an os upgrade...

[kozyilmaz]

Hey @kalamarcito one sec, have you tried with:

1. this Nvidia driver (and maybe there may be an updated one too) http://www.nvidia.com/download/driverResults.aspx/120845/en-us
2. CUDA Toolkit 9.1
3. Xcode 9.2
   Maybe you don't have to upgrade after all?

[kalamarcito]

That one is the driver pre security update, it refuses to install on 10.12.6 (16G1212), it asks for 10.12.6 (16G29) (actually tried it).

When you are on 16G29 and apply the security update to 16G1212, that driver stops working and asks to be updated. This is standard behaviour through OSX updates.

Now I installed CUDA Toolkit 9.1, the web says it's for High Sierra and driver version 390 (while driver for 16G1212 is 378...) yet it installed anyway.

make detects the 9.1 toolkit, yet it still fails. Sometimes it fails installing autoconf, sometimes configuring cmake. I tried as regular and super user.

I'm not too worried, I'm just a hobbyst, but if this happens to someone else and I may help further, just ask, I'll be happy to. Thanks for your support anyway.

PS: I'm wondering whether it has something to do with the CLI tools required. Perhaps removing the assertion and trying to compile with the updated tools... I'll try that later

[kalamarcito]

tried and it fails while installing libtool (as a regular user), installing autoconf (as an admin) or configuring cmake (as root)

[kozyilmaz]

Do you have brew installed? You don't have to try as superuser, I didn't even tested that. Can you build with:
$ PRINT_DEBUG=y make all

[kalamarcito]

• installed brew, failed compilation
• then ran PRINT_DEBUG=y make all, saw a lot of permission denied so I deleted the whole folder and cloned again (as regular user from now on)
• now fasm site seems to be down, time for a walk and try later
  Thanks a lot! I think I'm getting closer

[kozyilmaz]

No, if you don't use it please uninstall brew
This repo is tested with vanilla macOS and it is self contained (except Nvidia and Apple tools of course)

[kalamarcito]

What I use and was always installed is fink
Anyway I think the compilation problems came from those permission issues and the thing will compile when fasm comes online again. All the compile errors were thrown while building the self contained dependencies.