Jetson TX2 & Arrayfire

[Philip Cox]

We're about to port an app (which calls to arrayfire) onto a Jetson TX2. Are there any issues we need to be aware of? For instance, I noticed that the latest Jetson installer (jetpack) installs Cuda 9.0, and i'm not sure that this is yet supported under Arrayfire.   Any hints very welcome.

[Pradeep Garigipati]

Current release, v3.5.1, doesn't work with CUDA 9. However, we are almost close to doing the v3.6 release in the next few days and that will be shipped with CUDA 9. We are not doing a tegra release along with other OSes due to non-technical reasons, but we will do it soon.

Having said that, the current master works with CUDA 9 and you should be able to compile current master on tegra, out of the box. If you face any issues, feel free to post them on our github and we will look into them. 

We will try our best to get out the tegra release, soon.

On Fri 20 Apr, 2018, 12:22 PM Philip Cox, <phili...@cisra.canon.com.au> wrote:

We're about to port an app (which calls to arrayfire) onto a Jetson TX2. Are there any issues we need to be aware of? For instance, I noticed that the latest Jetson installer (jetpack) installs Cuda 9.0, and i'm not sure that this is yet supported under Arrayfire.   Any hints very welcome.

--
You received this message because you are subscribed to the Google Groups "ArrayFire Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to arrayfire-use...@googlegroups.com.
To post to this group, send email to arrayfi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/arrayfire-users/40741afc-a31b-42f3-af53-a4974f9a684a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[David Battle]

Hi, I'm actually attempting to compile AF 3.6 on a TX1 with L4T 3.2 (CUDA 9.0) now and have run into a few problems. At the end of make install, there is a failure to find build/third_party/forge/lib

Any pointers?

Cheers,

David.

[Pradeep Garigipati]

Does the 'third_party/forge' have contents at all?

Try running 'make forge-ext' command. That should give us a better clue as to why forge didn't build.

To view this discussion on the web visit https://groups.google.com/d/msgid/arrayfire-users/3fe8cb0b-0b12-4128-958e-768dbd016552%40googlegroups.com.

[David Battle]

Hi Pradeep,

Tried making forge-ext in third_party/forge/src/forge-ext but got:

CMake Error at CMakeLists.txt:54 (find_package):
By not providing "Findglm.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "glm", but
CMake did not find one.

Could not find a package configuration file provided by "glm" with any of
the following names:

glmConfig.cmake
glm-config.cmake

I ended up commenting out some lines in cmake_install.cmake thus
#if(NOT CMAKE_INSTALL_COMPONENT OR "${CMAKE_INSTALL_COMPONENT}" STREQUAL
#"common_backend_dependencies")
# file(INSTALL DESTINATION "${CMAKE_INSTALL_PREFIX}/lib" TYPE DIRECTORY
FILES "/home/nvidia/#arrayfire/build/third_party/forge/lib/")
#endif()

to get arrayfire to install.

[Pradeep Garigipati]

That won't help you I believe because the problem is due to upstream forge library. Forge cmake configure step is failing because of lack of glm header-only library. Do you have glm installed ?

--
You received this message because you are subscribed to the Google Groups "ArrayFire Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to arrayfire-use...@googlegroups.com.
To post to this group, send email to arrayfi...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/arrayfire-users/3b432d80-042a-5b5c-3ed6-bdce073a21b6%40missionsystems.com.au.

[David Battle]

Have definitely installed glm, but make install still can't find
third_party/forge/lib.

(third_party/forge directory only has directories src and tmp).

As I was only interested in some FFT timings, I managed to install with
graphics OFF by commenting cmake_install.cmake as described, but of
course, not a real solution.

[Pradeep Garigipati]

You can disable graphics using the cmake option `AF_WITH_GRAPHICS`. You can do so by running cmake as following

cmake .. -DAF_WITH_GRAPHICS:BOOL=OFF

No need to modify the source files.

How did you install glm ? Can you find glmConfig.cmake or glm-config.cmake files on your machine ? If you have `locate` command, try to find those files on your system.

[David Battle]

BTW: Switching graphics back ON and compiling throws up this error,
which might be the cause of the problem:

[ 37%] No patch step for 'glfw-Release'
[ 50%] No update step for 'glfw-Release'
[ 62%] Performing configure step for 'glfw-Release'
loading initial cache file
/home/nvidia/.hunter/_Base/efd84db/4d5b26e/43a539c/cache.cmake
loading initial cache file
/home/nvidia/.hunter/_Base/efd84db/4d5b26e/43a539c/Build/glfw/args.cmake
CMake Error at CMakeLists.txt:1 (cmake_minimum_required):
CMake 3.8 or higher is required. You are running version 3.5.1


-- Configuring incomplete, errors occurred!

[Pradeep Garigipati]

I was assuming you are doing an out-of-source build. hence I used cmake .. along with the option. Please do bare that .. should be replaced to the path where main CMakeLists.txt file of ArrayFire repo is present.

[Pradeep Garigipati]

We started using hunter for Linux builds. Looks like hunter package for glfw uses 3.8 CMake as minimum required version. Note that glfw project itself doesn't do that. So this is a change from hunter.

Can you try removing the line https://github.com/arrayfire/arrayfire/blob/master/CMakeModules/build_forge.cmake#L43 from build_forge.cmake file under CMakeModules folder. You may get some errors depending on what forge dependencies you have installed.

If possible, can you please come online over slack arrayfire slack it would be easy to exchange messages.

[Pradeep Garigipati]

As of v3.6 release, which we just did couple of days back, the minimum required version of arrayfire is 3.0. The above discussed issue with hunter requesting for 3.8 is not a problem anymore. Please recheck your setup and do a clean build.