jason-tilley

Well a new OS, and a new set of problems. It won't go pas the configure phase now. Now I'm getting ``` configure.ac:103: error: possibly undefined macro: AC_MSG_ERROR If this...

OK, it was a curl dependency issue. Now it reaches the build phase. I'm now getting some errors related to swab32. ``` :info:build ptxas info : Used 63 registers, 344...

That is strange, because it did that even when compiling with gcc7. It seems to be getting much further, but I have a new error now: ``` :info:build /usr/local/cuda/bin/nvcc -gencode=arch=compute_61,code=sm_61...

Still fails... here is the code. I will also make sure I am using the correct C++ library. ``` :info:build /usr/bin/clang++ -DHAVE_CONFIG_H -I. -I/opt/local/include -I/opt/local/include -fno-strict-aliasing -I/usr/local/cuda/include -DUSE_WRAPNVML -DSCRYPT_KECCAK512 -DSCRYPT_CHACHA...

Look like I am using libc++, which supports C++11 if I am not mistaken.

When I set with -std=c++11 I get a similar error. To be clear, should I still have -stdlib=libc++ set as a cxx flag? ``` :info:build /usr/local/cuda/bin/nvcc -gencode=arch=compute_61,code=sm_61 -gencode=arch=compute_52,code=sm_52 -gencode=arch=compute_50,code=sm_50 -gencode=arch=compute_37,code=sm_37...

Thanks. Sorry, I know little about this stuff. How do I add that as an nvcc option?

I did not. I will look that over tomorrow. Thanks.

I did not see any cuda options in build.sh, but I saw some cuda configuration options in configure.sh. I added -std=c++11 after Xcompiler, but it still isn't putting it in...

Although I'm looking at this, and I'm noticing it is looking for libnvidia-ml.so, which as far as I know doesn't come with the Mac CUDA drivers. I believe the proper...