Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GPU engine in DNNL disabled by default #938

Closed
blueberry opened this issue Aug 25, 2020 · 51 comments
Closed

GPU engine in DNNL disabled by default #938

blueberry opened this issue Aug 25, 2020 · 51 comments

Comments

@blueberry
Copy link

javacpp ships DNNL with the GPU engine disabled. This is the default build in upstream DNNL:

GPU Engine
Intel Processor Graphics and Xe architecture-based Graphics are supported by the oneDNN GPU engine. The GPU engine is > disabled in the default build configuration. The following additional requirements apply when GPU engine is enabled:

OpenCL* runtime library (OpenCL version 1.2 or later)
OpenCL driver (with kernel language support for OpenCL C 2.0 or later) with Intel subgroups extension support

What is required to enable it in javacpp (by default)? Does the absence of javacpp preset for OpenCL block it, or it it not required, but you simply chose to follow the DNNL default?

@saudet
Copy link
Member

saudet commented Aug 25, 2020

No idea, OpenCV builds and runs fine with OpenCL enabled. Would you mind inquiring upstream?

@blueberry
Copy link
Author

@saudet Thanks! I've opened the issue upstream. oneapi-src/oneDNN#823

@saudet
Copy link
Member

saudet commented Aug 25, 2020

It looks like DNNL doesn't link with libOpenCL.so.1, etc dynamically, so we'll need to create a -gpu extension for this.
Probably the easiest one to use as a template for this are the presets for ONNX Runtime:
https://github.com/bytedeco/javacpp-presets/tree/master/onnxruntime
If you could try to patch this up together and send a pull request, it would help!

@blueberry
Copy link
Author

Yes, I'll investigate this. If I understand correctly, that extension would give the user a choice to either use javacpp's dnnl default, or the one where both cpu and gpu are enabled (*-gpu extension)? That would be great, since both the "safe and stable" and "all features on" are available.

@saudet
Copy link
Member

saudet commented Aug 25, 2020

Yes, that's correct, and it can fall back automatically on the CPU-only binary when the GPU one fails to load.

BTW, it seems to support only Intel GPUs on Linux and Windows (Mac isn't supported), so I'm not sure if it's worth the trouble.

@blueberry
Copy link
Author

If I understood correctly, based on the CPU use cases, the idea is not that these engines are exclusive, but that, similarly to OpenCL, you query the DNNL library for available engines, select the one you like (there can be even more than one CPU engine), and use it. So, the same binary should be able to load both CPU and GPU. But I might be wrong (but then the related DNNL API doesn't make much sense).

As GPU part is disabled by the default build, the query for engines will only return the CPU engine. As for whether it's worth the effort, I thought that all underlying specifics are handled by DNNL, so from the user's point of view, including GPU in the build would enable more options, which shouldn't hurt. Most Intel's GPUs would not be competitive even with CPUs, but, on the other hand, Intel seems to be stepping up their game, so increasingly better options might be available soon.

Anyway, this is not a priority, but would be nice to have at least for experimentation...

@blueberry
Copy link
Author

Here's what the DNNL folks say:

When you build oneDNN with OpenCL runtime the library will be dependent on OpenCL Installable Client Driver (libOpenCL.so):

$ ldd libdnnl.so.1
linux-vdso.so.1 (0x00007ffe3a532000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fedfe459000)
libOpenCL.so.1 => /lib/x86_64-linux-gnu/libOpenCL.so.1 (0x00007fedfe24e000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fedfe248000)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fedfe067000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fedfdf18000)
libgomp.so.1 => /lib/x86_64-linux-gnu/libgomp.so.1 (0x00007fedfded6000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fedfdeb9000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fedfdcc7000)
/lib64/ld-linux-x86-64.so.2 (0x00007fee00732000)
So if ICD is not available in the system the application will fail. It does not matter whether Intel OpenCL Runtime is actually available or not, what matters is the loader. I believe ICD is available on most systems out of the box. Other than that CPU engine should work as expected.

In our case, can javacpp's DNNL ship with libopencl.so included? (I guess that would be it, but it's better to check before I try messing up with the build. In that case, do I have to configure that manually, or javacpp will figure it out and include it automatically?)

@saudet
Copy link
Member

saudet commented Aug 26, 2020

If I understood correctly, based on the CPU use cases, the idea is not that these engines are exclusive, but that, similarly to OpenCL, you query the DNNL library for available engines, select the one you like (there can be even more than one CPU engine), and use it. So, the same binary should be able to load both CPU and GPU. But I might be wrong (but then the related DNNL API doesn't make much sense).

The API doesn't look that easy to use to me. You're probably looking more for something like ONNX Runtime.

Anyway, this is not a priority, but would be nice to have at least for experimentation...

Sure, we probably just need to add the -DDNNL_GPU_RUNTIME=OCL build flag to experiment. Please give it a try!

In our case, can javacpp's DNNL ship with libopencl.so included? (I guess that would be it, but it's better to check before I try messing up with the build. In that case, do I have to configure that manually, or javacpp will figure it out and include it automatically?)

Like I said, if we create an -gpu extension, it can fall back on the CPU-only binary, so we don't need to try to bundle OpenCL. (Unless you do also want to create presets for OpenCL, and then that would make sense, yes.)

@blueberry
Copy link
Author

blueberry commented Aug 26, 2020

The API doesn't look that easy to use to me. You're probably looking more for something like ONNX Runtime.

I already use DNNL and, though the API could be much more straightforward, I use it through my wrappers that simplify the use a lot, so I'm fine with it :)

Anyway, this is not a priority, but would be nice to have at least for experimentation...

Sure, we probably just need to add the -DDNNL_GPU_RUNTIME=OCL build flag to experiment. Please give it a try!

Will do!

@blueberry
Copy link
Author

This is just a note that I haven't forgotten this. I was just overwhelmed with other pressing work. I plan to do this within the next two weeks.

@saudet
Copy link
Member

saudet commented Sep 12, 2020

I've enabled the OpenCL backend by default for Linux in the latest commit. Maybe we can reasonably assume that almost all users will have libOpenCL.so.1 somewhere on their systems. We'll see if anyone complains about this with the snapshots, and if not, maybe we'll be able to release it like that.

@blueberry
Copy link
Author

blueberry commented Sep 17, 2020

Hi @saudet

Thank you!
I've took time today to work on this, and the first thing that I tried is, of course, to try the snapshots. Good thing is that the things that worked before still work. The bad part is that it seems that I can't try the new functionality because my Intel platform on i7-4790k does not support its meager integrated GPU. I have 3 OpenCL platforms on this computer (Intel, AMD, and Nvidia), and I expected that Intel's expose its GPU, but it doesn't.

I have two newer computers, but neither of them has an integrated GPU, since they are a combination of powerful Inetl CPU and a recent Nvidia GPU.

Related to the libOpenCL issue. Is this going to work as before if a user doesn't have libOpenCL? I've moved that file temporarily just to try this out, and it doesn't make any difference. The old code still works, and the library doesn't even try to load libOpenCL, although I've tried to list GPU engines in the appropriate DNNL api.

In that regard, it seems that the latest changes might be optimal:

  1. for existing users, everything works well even if OpenCL is not present
  2. if there is OpenCL and the appropriate hardware, the library should pick this up.

However, I haven't been able to test the 2nd point...

@saudet
Copy link
Member

saudet commented Sep 18, 2020

OpenCL doesn't need to be present, but a library named libOpenCL.so.1 still needs to be loaded from somewhere. You probably have a couple of those lying around on your system, and that's why it's still loading without error.

@blueberry
Copy link
Author

Hmmm, I thought so, but then when I remove that libOpenCL.so, clinfo does break and complains that there's no libopencl available...

@saudet
Copy link
Member

saudet commented Sep 18, 2020

clinfo might be looking for libOpenCL.so, I'm not sure, but that's not the file that matters here.
The one that matters is libOpenCL.so.1, with a .1 after .so.

@blueberry
Copy link
Author

I was writing from the top of my head. This is the exact file I removed: /usr/lib/libOpenCL.so.1.0.0

@blueberry
Copy link
Author

... and both libOpenCL.so and libOpenCL.so.1 are soft links to the libOpenCL.so.1.0.0...

@saudet
Copy link
Member

saudet commented Sep 18, 2020

What does ldd $(which clinfo) return?

@blueberry
Copy link
Author

linux-vdso.so.1 (0x00007fff1c345000)
	libOpenCL.so.1 => /usr/lib/libOpenCL.so.1 (0x00007f563a6bf000)
	libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f563a6b9000)
	libc.so.6 => /usr/lib/libc.so.6 (0x00007f563a4f0000)
	librt.so.1 => /usr/lib/librt.so.1 (0x00007f563a4e5000)
	libm.so.6 => /usr/lib/libm.so.6 (0x00007f563a39f000)
	libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f563a37d000)
	/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007f563a924000)

@saudet
Copy link
Member

saudet commented Sep 18, 2020

And if you remove /usr/lib/libOpenCL.so.1, what's the output?

@blueberry
Copy link
Author

clinfo: error while loading shared libraries: libOpenCL.so.1: cannot open shared object file: No such file or directory

@blueberry
Copy link
Author

At the same time, my code using javacpp dnnl platform "1.6.2-1.5.5-SNAPSHOT" is loading without problems.

@blueberry
Copy link
Author

I mean, that's not a bug, that's a wonderful feature! We just have to make sure there's not something else at play here. Because I don't think that the majority of users have opencl installed....

@saudet
Copy link
Member

saudet commented Sep 20, 2020

Try again with 1.6.3-1.5.5-SNAPSHOT to make sure it's not using some old binaries from somewhere...

@blueberry
Copy link
Author

Still working without libOpenCL.so.1.

@saudet
Copy link
Member

saudet commented Nov 6, 2020

@blueberry
Copy link
Author

Hmmm. That seems quite logical. I'm puzzled how it works on my machine when I remove libOpenCL.so (and .1 etc.)...

@saudet
Copy link
Member

saudet commented Dec 16, 2020

I've added presets for OpenCL, and made DNNL depend on them, so it can use the OpenCL libraries from them. They don't need to be installed on the system anymore. OpenCL is now enabled for both Linux and Windows builds. Let me know if you're having any issues with that though! Thanks

@blueberry
Copy link
Author

Thanks! I'll check it out. Additionally, it might be a good opportunity to try to support the new OpenCL bindings in my libraries. I see that you support OpenCL 3.0. Are they compatible with existing OpenCL 2.0? I remember that when they announced OpenCL 3.0 they mentioned that it's based on 1.2, but 2.0 is supported for existing implementations, but I was confused what that actually meant...

@saudet
Copy link
Member

saudet commented Dec 16, 2020

Right, OpenCL 3.0 is basically OpenCL 1.2 with everything from 2.0 as optional extensions. That way, they are making NVIDIA GPUs compliant with the latest version of OpenCL :)

@blueberry
Copy link
Author

Thanks. I meant: would I be able to port existing OpenCL 2.0 code to bytedeco's OpenCL 3.0? Are the functions that I'd expect in OpenCL 2.0 available somewhere in bytedeco's bindings? (I'm not sure what being an extension means regarding a Java JNI binding).

@saudet
Copy link
Member

saudet commented Dec 16, 2020

Everything from OpenCL 2.x is available, yes, it will just error out if you try to call those functions on a GPU from NVIDIA:
https://github.com/bytedeco/javacpp-presets/blob/master/opencl/src/gen/java/org/bytedeco/opencl/global/OpenCL.java

@blueberry
Copy link
Author

That's great news. I'll definitely check this out and see how to integrate it in my libraries. Will cry for help if I stumble on a problem, I hope you wouldn't mind :)

junlarsen pushed a commit to junlarsen/javacpp-presets that referenced this issue Dec 23, 2020
@saudet
Copy link
Member

saudet commented Mar 10, 2021

OpenCL-enabled builds of DNNL 2.1.1 have now been released with version 1.5.5. Enjoy!

@blueberry
Copy link
Author

@saudet It seems that system-wide OpenCL 3.0 is needed, but only if Nvidia's cuDNN is loaded. I'm currently using JCuda's cuDNN, so I'm not sure whether this would appear if I used JavaCPP's cuDNN, but the exception is raised by JavaCPP, which I use via DNNL. Please see this issue (I solved that on my machine by installing Intel's OpenCL and generic OpenCL 3.0 loader alongside the OpenCL that comes with CUDA).

uncomplicate/deep-diamond#12

@blueberry
Copy link
Author

Personally, this is not an issue to me, since I solved it by system wide OpenCL 3.0, but some users who use DNNL/CUDA might be hit by a similar discrepancy issue.

@saudet
Copy link
Member

saudet commented May 20, 2021

NVIDIA doesn't support using multiple versions of CUDA like that in the same application. You should use only a single version of CUDA in any given application. If you wish to use libraries from the JavaCPP Presets built with a different version of CUDA than is supported by JCuda, it's going to cause issues like that.

@blueberry
Copy link
Author

Hmmmm, I'm not sure I follow. I don't use any JavaCPP CUDA (10.2 or other). I use JavaCPP DNNL stable 1.5.5 (which, as I understand, pulls some JavaCPP OpenCL dependency), and JCuda's CUDA 10.2. Both JCuda and JavaCPP CUDA (stable) link to CUDA 10.2, but is that relevant at all, since I don't pull JavaCPP CUDA dependency at all?

@saudet
Copy link
Member

saudet commented May 21, 2021

JCuda or something is obviously loading an old version of OpenCL. That's not going to work.

@saudet
Copy link
Member

saudet commented May 21, 2021

It looks like you're loading JOCL that doesn't support OpenCL 3.0 in here:
https://github.com/uncomplicate/neanderthal/search?q=jocl
That's probably what is causing the problem here.

@blueberry
Copy link
Author

Could be that, but, curiously, everything works well if the system-wide platform is up-to date (in my case, installing ocl-icd and Intel's OpenCL; I'm not sure which of these two solved it).
Do you think that giving JavaCPP a chance to load OpenCL before that point would solve the issue?

@saudet
Copy link
Member

saudet commented May 21, 2021

Possibly, yes, but like I said, it's never a good idea to try to run multiple versions of the same library in the same application, whether it be Java, CUDA, OpenCL, etc. Don't do that!

@blueberry
Copy link
Author

You are right about that!

I just can't pinpoint the point where the collision happens, since in this case no OpenCL should be loaded at all, since:

  1. The namespace you've mentioned shouldn't even be loaded, since clblast is not used nor referenced from cublas-related code, which is used by cudnn-related code.
  2. JavaCPP DNNL tries to load (or work with) OpenCL implicitly. It puzzles me why there is collision at all.

@saudet
Copy link
Member

saudet commented May 21, 2021

You can set the "org.bytedeco.javacpp.logger.debug" system property to "true" to get more information at load time.

@blueberry
Copy link
Author

Thanks!

@qeshi
Copy link

qeshi commented May 21, 2021

Hi!
I openened uncomplicate/deep-diamond#12

I turned on debugging and this is the output I got:

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Debug: Loading class org.bytedeco.javacpp.presets.javacpp
Debug: Loading class org.bytedeco.javacpp.Loader
Debug: Loading /home/ubuntu/.javacpp/cache/javacpp-1.5.5-linux-x86_64.jar/org/bytedeco/javacpp/linux-x86_64/libjnijavacpp.so
Debug: Loading class org.bytedeco.javacpp.presets.javacpp
Debug: Loading class org.bytedeco.javacpp.Pointer
Debug: Loading class org.bytedeco.javacpp.presets.javacpp
Debug: Loading class org.bytedeco.opencl.global.OpenCL
Debug: Loading class org.bytedeco.javacpp.presets.javacpp
Debug: Loading class org.bytedeco.opencl.global.OpenCL
Debug: Loading /home/ubuntu/.javacpp/cache/opencl-3.0-1.5.5-linux-x86_64.jar/org/bytedeco/opencl/linux-x86_64/libOpenCL.so.1
Debug: Loading /home/ubuntu/.javacpp/cache/opencl-3.0-1.5.5-linux-x86_64.jar/org/bytedeco/opencl/linux-x86_64/libjniOpenCL.so
Debug: Failed to load /home/ubuntu/.javacpp/cache/opencl-3.0-1.5.5-linux-x86_64.jar/org/bytedeco/opencl/linux-x86_64/libjniOpenCL.so: java.lang.UnsatisfiedLinkError: /home/ubuntu/.javacpp/cache/opencl-3.0-1.5.5-linux-x86_64.jar/org/bytedeco/opencl/linux-x86_64/libjniOpenCL.so: /usr/local/cuda-11.2/lib64/libOpenCL.so: version `OPENCL_2.2' not found (required by /home/ubuntu/.javacpp/cache/opencl-3.0-1.5.5-linux-x86_64.jar/org/bytedeco/opencl/linux-x86_64/libjniOpenCL.so)
Debug: Loading library jniOpenCL
Debug: Failed to load for jniOpenCL: java.lang.UnsatisfiedLinkError: no jniOpenCL in java.library.path: [/home/ubuntu/.javacpp/cache/mkl-2021.1-1.5.5-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_rt.so, /home/ubuntu/.javacpp/cache/mkl-2021.1-1.5.5-linux-x86_64.jar/org/bytedeco/mkl/linux-x86_64, /usr/local/cuda-11.2/lib64, /home/ubuntu/.javacpp/cache/mkl-2021.1-1.5.5-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_rt.so, /home/ubuntu/.javacpp/cache/mkl-2021.1-1.5.5-linux-x86_64.jar/org/bytedeco/mkl/linux-x86_64, /usr/local/cuda-11.3/lib64, ., /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Execution error (UnsatisfiedLinkError) at java.lang.ClassLoader$NativeLibrary/load0 (ClassLoader.java:-2).
/home/ubuntu/.javacpp/cache/opencl-3.0-1.5.5-linux-x86_64.jar/org/bytedeco/opencl/linux-x86_64/libjniOpenCL.so: /usr/local/cuda-11.2/lib64/libOpenCL.so: version `OPENCL_2.2' not found (required by /home/ubuntu/.javacpp/cache/opencl-3.0-1.5.5-linux-x86_64.jar/org/bytedeco/opencl/linux-x86_64/libjniOpenCL.so)

@blueberry
Copy link
Author

@qeshi Your cuda path (/usr/local/cuda-11.3/lib64) suggests that you have CUDA 11.3, whereas JCuda (and JavaCPP 1.5.5 CUDA too) has been built with CUDA 11.2. Please make sure that CUDA 11.2 is installed, instead of 11.3.

@qeshi
Copy link

qeshi commented May 21, 2021

Ok!
I created a new clean Ubuntu Server 20.04 LTS EC2 instance and installed cuda_11.2.0_460.27.04_linux and clojure on it.

Now I get this exception.

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Execution error (UnsatisfiedLinkError) at java.lang.ClassLoader$NativeLibrary/load0 (ClassLoader.java:-2).
/tmp/libneanderthal-mkl-0.33.07378310562563551434.so: libmkl_rt.so: cannot open shared object file: No such file or directory

I solved this before by adding /home/ubuntu/.javacpp/cache/mkl-2021.1-1.5.5-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_rt.so to a textfile in /etc/ld.so.conf.d/ and running sudo ldconfig but I'm not sure this is the correct way of doing things and this is maybe causing my problems.

Should I just install sudo apt-get install intel-mkl instead?

I tried to use [org.bytedeco/mkl-platform-redist "2020.3-1.5.4"] in the deep-diamond project, and got the following exceptions.

Debug: Loading class org.bytedeco.javacpp.presets.javacpp
Debug: Loading class org.bytedeco.javacpp.Loader
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/javacpp/1.5.5/javacpp-1.5.5-linux-x86_64.jar!/org/bytedeco/javacpp/linux-x86_64/libjnijavacpp.so
Debug: Loading /home/ubuntu/.javacpp/cache/javacpp-1.5.5-linux-x86_64.jar/org/bytedeco/javacpp/linux-x86_64/libjnijavacpp.so
Debug: Loading class org.bytedeco.javacpp.presets.javacpp
Debug: Loading class org.bytedeco.javacpp.Pointer
Warning: Versions of org.bytedeco:javacpp:1.5.5 and org.bytedeco:mkl:2020.3-1.5.4 do not match.
Debug: Loading class org.bytedeco.javacpp.presets.javacpp
Debug: Loading class org.bytedeco.mkl.global.mkl_rt
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/mkl/2020.3-1.5.4/mkl-2020.3-1.5.4-linux-x86_64-redist.jar!/org/bytedeco/mkl/linux-x86_64/libmkl_core.so
Debug: Loading /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_core.so
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/mkl/2020.3-1.5.4/mkl-2020.3-1.5.4-linux-x86_64-redist.jar!/org/bytedeco/mkl/linux-x86_64/libiomp5.so
Debug: Loading /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libiomp5.so
Debug: Loading library libiomp5md
Debug: Failed to load for libiomp5md: java.lang.UnsatisfiedLinkError: no libiomp5md in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/mkl/2020.3-1.5.4/mkl-2020.3-1.5.4-linux-x86_64-redist.jar!/org/bytedeco/mkl/linux-x86_64/libmkl_gnu_thread.so
Debug: Loading /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_gnu_thread.so
Debug: Failed to load /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_gnu_thread.so: java.lang.UnsatisfiedLinkError: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_gnu_thread.so: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_gnu_thread.so: undefined symbol: mkl_blas_dgemm_blk_info_bdz
Debug: Loading library mkl_gnu_thread
Debug: Failed to load for mkl_gnu_thread: java.lang.UnsatisfiedLinkError: no mkl_gnu_thread in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/mkl/2020.3-1.5.4/mkl-2020.3-1.5.4-linux-x86_64-redist.jar!/org/bytedeco/mkl/linux-x86_64/libmkl_intel_lp64.so
Debug: Loading /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_intel_lp64.so
Debug: Failed to load /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_intel_lp64.so: java.lang.UnsatisfiedLinkError: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_intel_lp64.so: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_intel_lp64.so: undefined symbol: mkl_lapack_zhesvxx
Debug: Loading library mkl_intel_lp64
Debug: Failed to load for mkl_intel_lp64: java.lang.UnsatisfiedLinkError: no mkl_intel_lp64 in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/mkl/2020.3-1.5.4/mkl-2020.3-1.5.4-linux-x86_64-redist.jar!/org/bytedeco/mkl/linux-x86_64/libmkl_intel_thread.so
Debug: Loading /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_intel_thread.so
Debug: Failed to load /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_intel_thread.so: java.lang.UnsatisfiedLinkError: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_intel_thread.so: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_intel_thread.so: undefined symbol: mkl_blas_dgemm_blk_info_bdz
Debug: Loading library mkl_intel_thread
Debug: Failed to load for mkl_intel_thread: java.lang.UnsatisfiedLinkError: no mkl_intel_thread in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/mkl/2020.3-1.5.4/mkl-2020.3-1.5.4-linux-x86_64-redist.jar!/org/bytedeco/mkl/linux-x86_64/libmkl_def.so
Debug: Loading /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_def.so
Debug: Failed to load /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_def.so: java.lang.UnsatisfiedLinkError: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_def.so: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_def.so: undefined symbol: mkl_sparse_optimize_bsr_trsm_i8
Debug: Loading library mkl_def
Debug: Failed to load for mkl_def: java.lang.UnsatisfiedLinkError: no mkl_def in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/mkl/2020.3-1.5.4/mkl-2020.3-1.5.4-linux-x86_64-redist.jar!/org/bytedeco/mkl/linux-x86_64/libmkl_mc.so
Debug: Loading /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_mc.so
Debug: Failed to load /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_mc.so: java.lang.UnsatisfiedLinkError: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_mc.so: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_mc.so: undefined symbol: mkl_sparse_optimize_bsr_trsm_i8
Debug: Loading library mkl_mc
Debug: Failed to load for mkl_mc: java.lang.UnsatisfiedLinkError: no mkl_mc in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/mkl/2020.3-1.5.4/mkl-2020.3-1.5.4-linux-x86_64-redist.jar!/org/bytedeco/mkl/linux-x86_64/libmkl_mc3.so
Debug: Loading /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_mc3.so
Debug: Failed to load /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_mc3.so: java.lang.UnsatisfiedLinkError: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_mc3.so: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_mc3.so: undefined symbol: mkl_sparse_optimize_bsr_trsm_i8
Debug: Loading library mkl_mc3
Debug: Failed to load for mkl_mc3: java.lang.UnsatisfiedLinkError: no mkl_mc3 in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Loading library mkl_p4
Debug: Failed to load for mkl_p4: java.lang.UnsatisfiedLinkError: no mkl_p4 in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Loading library mkl_p4m
Debug: Failed to load for mkl_p4m: java.lang.UnsatisfiedLinkError: no mkl_p4m in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Loading library mkl_p4m3
Debug: Failed to load for mkl_p4m3: java.lang.UnsatisfiedLinkError: no mkl_p4m3 in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/mkl/2020.3-1.5.4/mkl-2020.3-1.5.4-linux-x86_64-redist.jar!/org/bytedeco/mkl/linux-x86_64/libmkl_avx.so
Debug: Loading /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_avx.so
Debug: Failed to load /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_avx.so: java.lang.UnsatisfiedLinkError: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_avx.so: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_avx.so: undefined symbol: mkl_sparse_optimize_bsr_trsm_i8
Debug: Loading library mkl_avx
Debug: Failed to load for mkl_avx: java.lang.UnsatisfiedLinkError: no mkl_avx in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/mkl/2020.3-1.5.4/mkl-2020.3-1.5.4-linux-x86_64-redist.jar!/org/bytedeco/mkl/linux-x86_64/libmkl_avx2.so
Debug: Loading /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_avx2.so
Debug: Failed to load /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_avx2.so: java.lang.UnsatisfiedLinkError: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_avx2.so: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_avx2.so: undefined symbol: mkl_sparse_optimize_bsr_trsm_i8
Debug: Loading library mkl_avx2
Debug: Failed to load for mkl_avx2: java.lang.UnsatisfiedLinkError: no mkl_avx2 in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/mkl/2020.3-1.5.4/mkl-2020.3-1.5.4-linux-x86_64-redist.jar!/org/bytedeco/mkl/linux-x86_64/libmkl_avx512.so
Debug: Loading /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_avx512.so
Debug: Failed to load /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_avx512.so: java.lang.UnsatisfiedLinkError: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_avx512.so: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_avx512.so: undefined symbol: mkl_sparse_optimize_bsr_trsm_i8
Debug: Loading library mkl_avx512
Debug: Failed to load for mkl_avx512: java.lang.UnsatisfiedLinkError: no mkl_avx512 in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/mkl/2020.3-1.5.4/mkl-2020.3-1.5.4-linux-x86_64-redist.jar!/org/bytedeco/mkl/linux-x86_64/libmkl_avx512_mic.so
Debug: Loading /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_avx512_mic.so
Debug: Failed to load /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_avx512_mic.so: java.lang.UnsatisfiedLinkError: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_avx512_mic.so: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_avx512_mic.so: undefined symbol: mkl_sparse_optimize_bsr_trsm_i8
Debug: Loading library mkl_avx512_mic
Debug: Failed to load for mkl_avx512_mic: java.lang.UnsatisfiedLinkError: no mkl_avx512_mic in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/mkl/2020.3-1.5.4/mkl-2020.3-1.5.4-linux-x86_64-redist.jar!/org/bytedeco/mkl/linux-x86_64/libmkl_vml_def.so
Debug: Loading /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_def.so
Debug: Failed to load /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_def.so: java.lang.UnsatisfiedLinkError: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_def.so: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_def.so: undefined symbol: mkl_lapack_dspevd
Debug: Loading library mkl_vml_def
Debug: Failed to load for mkl_vml_def: java.lang.UnsatisfiedLinkError: no mkl_vml_def in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Loading library mkl_vml_ia
Debug: Failed to load for mkl_vml_ia: java.lang.UnsatisfiedLinkError: no mkl_vml_ia in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/mkl/2020.3-1.5.4/mkl-2020.3-1.5.4-linux-x86_64-redist.jar!/org/bytedeco/mkl/linux-x86_64/libmkl_vml_mc.so
Debug: Loading /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_mc.so
Debug: Failed to load /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_mc.so: java.lang.UnsatisfiedLinkError: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_mc.so: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_mc.so: undefined symbol: mkl_lapack_dspevd
Debug: Loading library mkl_vml_mc
Debug: Failed to load for mkl_vml_mc: java.lang.UnsatisfiedLinkError: no mkl_vml_mc in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/mkl/2020.3-1.5.4/mkl-2020.3-1.5.4-linux-x86_64-redist.jar!/org/bytedeco/mkl/linux-x86_64/libmkl_vml_mc2.so
Debug: Loading /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_mc2.so
Debug: Failed to load /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_mc2.so: java.lang.UnsatisfiedLinkError: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_mc2.so: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_mc2.so: undefined symbol: mkl_lapack_dspevd
Debug: Loading library mkl_vml_mc2
Debug: Failed to load for mkl_vml_mc2: java.lang.UnsatisfiedLinkError: no mkl_vml_mc2 in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/mkl/2020.3-1.5.4/mkl-2020.3-1.5.4-linux-x86_64-redist.jar!/org/bytedeco/mkl/linux-x86_64/libmkl_vml_mc3.so
Debug: Loading /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_mc3.so
Debug: Failed to load /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_mc3.so: java.lang.UnsatisfiedLinkError: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_mc3.so: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_mc3.so: undefined symbol: mkl_lapack_dspevd
Debug: Loading library mkl_vml_mc3
Debug: Failed to load for mkl_vml_mc3: java.lang.UnsatisfiedLinkError: no mkl_vml_mc3 in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Loading library mkl_vml_p4
Debug: Failed to load for mkl_vml_p4: java.lang.UnsatisfiedLinkError: no mkl_vml_p4 in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Loading library mkl_vml_p4m
Debug: Failed to load for mkl_vml_p4m: java.lang.UnsatisfiedLinkError: no mkl_vml_p4m in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Loading library mkl_vml_p4m2
Debug: Failed to load for mkl_vml_p4m2: java.lang.UnsatisfiedLinkError: no mkl_vml_p4m2 in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Loading library mkl_vml_p4m3
Debug: Failed to load for mkl_vml_p4m3: java.lang.UnsatisfiedLinkError: no mkl_vml_p4m3 in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/mkl/2020.3-1.5.4/mkl-2020.3-1.5.4-linux-x86_64-redist.jar!/org/bytedeco/mkl/linux-x86_64/libmkl_vml_avx.so
Debug: Loading /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_avx.so
Debug: Failed to load /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_avx.so: java.lang.UnsatisfiedLinkError: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_avx.so: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_avx.so: undefined symbol: mkl_lapack_dspevd
Debug: Loading library mkl_vml_avx
Debug: Failed to load for mkl_vml_avx: java.lang.UnsatisfiedLinkError: no mkl_vml_avx in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/mkl/2020.3-1.5.4/mkl-2020.3-1.5.4-linux-x86_64-redist.jar!/org/bytedeco/mkl/linux-x86_64/libmkl_vml_avx2.so
Debug: Loading /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_avx2.so
Debug: Failed to load /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_avx2.so: java.lang.UnsatisfiedLinkError: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_avx2.so: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_avx2.so: undefined symbol: mkl_lapack_dspevd
Debug: Loading library mkl_vml_avx2
Debug: Failed to load for mkl_vml_avx2: java.lang.UnsatisfiedLinkError: no mkl_vml_avx2 in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/mkl/2020.3-1.5.4/mkl-2020.3-1.5.4-linux-x86_64-redist.jar!/org/bytedeco/mkl/linux-x86_64/libmkl_vml_avx512.so
Debug: Loading /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_avx512.so
Debug: Failed to load /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_avx512.so: java.lang.UnsatisfiedLinkError: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_avx512.so: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_avx512.so: undefined symbol: mkl_lapack_dspevd
Debug: Loading library mkl_vml_avx512
Debug: Failed to load for mkl_vml_avx512: java.lang.UnsatisfiedLinkError: no mkl_vml_avx512 in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/mkl/2020.3-1.5.4/mkl-2020.3-1.5.4-linux-x86_64-redist.jar!/org/bytedeco/mkl/linux-x86_64/libmkl_vml_avx512_mic.so
Debug: Loading /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_avx512_mic.so
Debug: Failed to load /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_avx512_mic.so: java.lang.UnsatisfiedLinkError: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_avx512_mic.so: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_avx512_mic.so: undefined symbol: mkl_lapack_dspevd
Debug: Loading library mkl_vml_avx512_mic
Debug: Failed to load for mkl_vml_avx512_mic: java.lang.UnsatisfiedLinkError: no mkl_vml_avx512_mic in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/mkl/2020.3-1.5.4/mkl-2020.3-1.5.4-linux-x86_64-redist.jar!/org/bytedeco/mkl/linux-x86_64/libmkl_vml_cmpt.so
Debug: Loading /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_cmpt.so
Debug: Failed to load /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_cmpt.so: java.lang.UnsatisfiedLinkError: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_cmpt.so: /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_vml_cmpt.so: undefined symbol: mkl_lapack_dspevd
Debug: Loading library mkl_vml_cmpt
Debug: Failed to load for mkl_vml_cmpt: java.lang.UnsatisfiedLinkError: no mkl_vml_cmpt in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/mkl/2020.3-1.5.4/mkl-2020.3-1.5.4-linux-x86_64-redist.jar!/org/bytedeco/mkl/linux-x86_64/libmkl_rt.so
Debug: Loading /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_rt.so
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/mkl/2020.3-1.5.4/mkl-2020.3-1.5.4-linux-x86_64.jar!/org/bytedeco/mkl/linux-x86_64/libjnimkl_rt.so
Debug: Creating symbolic link /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64.jar/org/bytedeco/mkl/linux-x86_64/libmkl_core.so to /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_core.so
Debug: Creating symbolic link /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64.jar/org/bytedeco/mkl/linux-x86_64/libiomp5.so to /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libiomp5.so
Debug: Creating symbolic link /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64.jar/org/bytedeco/mkl/linux-x86_64/libmkl_rt.so to /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64-redist.jar/org/bytedeco/mkl/linux-x86_64/libmkl_rt.so
Debug: Loading /home/ubuntu/.javacpp/cache/mkl-2020.3-1.5.4-linux-x86_64.jar/org/bytedeco/mkl/linux-x86_64/libjnimkl_rt.so
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Debug: Loading class org.bytedeco.javacpp.presets.javacpp
Debug: Loading class org.bytedeco.opencl.global.OpenCL
Debug: Loading class org.bytedeco.javacpp.presets.javacpp
Debug: Loading class org.bytedeco.opencl.global.OpenCL
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/opencl/3.0-1.5.5/opencl-3.0-1.5.5-linux-x86_64.jar!/org/bytedeco/opencl/linux-x86_64/libOpenCL.so.1
Debug: Loading /home/ubuntu/.javacpp/cache/opencl-3.0-1.5.5-linux-x86_64.jar/org/bytedeco/opencl/linux-x86_64/libOpenCL.so.1
Debug: Creating symbolic link /home/ubuntu/.javacpp/cache/opencl-3.0-1.5.5-linux-x86_64.jar/org/bytedeco/opencl/linux-x86_64/libOpenCL.so
Debug: Locking /home/ubuntu/.javacpp/cache before extracting
Debug: Extracting jar:file:/home/ubuntu/.m2/repository/org/bytedeco/opencl/3.0-1.5.5/opencl-3.0-1.5.5-linux-x86_64.jar!/org/bytedeco/opencl/linux-x86_64/libjniOpenCL.so
Debug: Loading /home/ubuntu/.javacpp/cache/opencl-3.0-1.5.5-linux-x86_64.jar/org/bytedeco/opencl/linux-x86_64/libjniOpenCL.so
Debug: Failed to load /home/ubuntu/.javacpp/cache/opencl-3.0-1.5.5-linux-x86_64.jar/org/bytedeco/opencl/linux-x86_64/libjniOpenCL.so: java.lang.UnsatisfiedLinkError: /home/ubuntu/.javacpp/cache/opencl-3.0-1.5.5-linux-x86_64.jar/org/bytedeco/opencl/linux-x86_64/libjniOpenCL.so: /usr/local/cuda-11.2/lib64/libOpenCL.so: version `OPENCL_2.2' not found (required by /home/ubuntu/.javacpp/cache/opencl-3.0-1.5.5-linux-x86_64.jar/org/bytedeco/opencl/linux-x86_64/libjniOpenCL.so)
Debug: Loading library jniOpenCL
Debug: Failed to load for jniOpenCL: java.lang.UnsatisfiedLinkError: no jniOpenCL in java.library.path: [/usr/local/cuda-11.2/lib64, /usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib]
Execution error (UnsatisfiedLinkError) at java.lang.ClassLoader$NativeLibrary/load0 (ClassLoader.java:-2).
/home/ubuntu/.javacpp/cache/opencl-3.0-1.5.5-linux-x86_64.jar/org/bytedeco/opencl/linux-x86_64/libjniOpenCL.so: /usr/local/cuda-11.2/lib64/libOpenCL.so: version `OPENCL_2.2' not found (required by /home/ubuntu/.javacpp/cache/opencl-3.0-1.5.5-linux-x86_64.jar/org/bytedeco/opencl/linux-x86_64/libjniOpenCL.so)

user=> Bye for now!

@blueberry
Copy link
Author

@qeshi Please follow https://neanderthal.uncomplicate.org/articles/getting_started.html
If there's any question, please browse Neanderthal/DD issues on github, and if that fails, open a new issue there. This is probably not a JavaCPP issue.

@qeshi
Copy link

qeshi commented May 21, 2021

sorry!

@saudet
Copy link
Member

saudet commented May 22, 2021

@qeshi There's something in your application that is incorrectly loading /usr/local/cuda-11.2/lib64/libOpenCL.so and it's not JavaCPP, so you'll need to figure out where that gets loaded, and fix that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants