CUDNN_jll conflict with Reactant

[goulf-3m]

In a test project with this:

using Reactant
using Lux
using LuxCUDA

Precompiling this project errors with:

Failed to precompile test [e061e0cf-51c1-4f7f-bc1b-3df52df7b1b7] to "/home/goulf/.julia/compiled/v1.11/test/jl_3TaEDK".
ERROR: LoadError: InitError: could not load library "/home/goulf/.julia/artifacts/2eb570b35b597d106228383c5cfa490f4bf538ee/lib/libcudnn
_cnn.so"
/home/goulf/.julia/artifacts/2eb570b35b597d106228383c5cfa490f4bf538ee/lib/libcudnn_cnn.so: undefined symbol: _ZTVN5cudnn7backend25Expan
dBandMatrixOperationE, version libcudnn_graph.so.9

With this (reording):

using Lux
using LuxCUDA
using Reactant

Precompilation succeeds!

[avik-pal]

We are probably shipping a binary with different version of cudnn compared to CUDNN.jl.

Any particular reason, you need to load both in the same session?

[goulf-3m]

When I want to compare Lux+Reactant+Enzyme and Lux+LuxCUDA+Zygote a single script.

If using standard CUDNN_jll is achievable for Reactant, shipping another should be avoided.
If not achievable, rename those libs (and symbols?) to avoid collision is more user-friendly. (Of course, lower priority compared to Reactant's core functionality)