Ralf Stubner

The error messages are different, though. What is the output of these commands? ```bash ldconfig --print-cache | grep libaf ldconfig --print-cache | grep libmkl ldd ```

> I installed ArrayFire from source too. Originally you mentioned **ArrayFire-v3.6.4_Linux_x86_64.sh**, which installs a pre-compiled binary. Are you still using that? Anyway, `ldconfig` not knowing about `libaf` is bad. Please...

You could try to manually configure the package. The `configure` script tries to locate the ArrayFire installation. It then takes `src/Makevars.in` and `R/flags.R.in` as input and replaces `@AF_INCLUDE@` and `@AF_LIBS`...

According to http://arrayfire.org/docs/using_on_windows.htm the ArrayFire installer sets an environment variable `AF_PATH`. Could you try to use the following as `src/Makevars.win`: ``` ## enviorment variables for building R package CXX_STD =...

Thanks for your tests! The Problem are the spaces in $AF_PATH, which `make` cannot handle. For now we have to go back to explicitly setting the paths in `src/Makevars`: ```...

> My ArrayFire install will run examples in Visual Studio with no problem. This hints at an issue: The ArrayFire libraries are compiled with Visual Studio, but the Rtools toolchain...

I have raised the question of building ArrayFire with mingw in their [slack community](https://arrayfire-org.slack.com/archives/C6M9AEJTB/p1516726675000977).

Response on slack was that it should work given that ArrayFire does not use any Visual C++ specialties on Windows. An alternative solution might be to build the R package...

I am not sure either. Good news is that I now have a Windows machine available and I intend to use it also for porting RcppArrayFire. I was already able...

I have made some progress with building ArrayFire using a mingw tool chain, but this is slow going ...