Closed GoogleCodeExporter closed 9 years ago
Thanks for reporting.
First I *assume* that you are running a 64 bit JVM... (java -version), I know
you may have checked already, but this is the error you will get if a 32 bit
JVM tries to load a 64 bit library.
My only concern is that the CUDA device is only OpenCL 1.1. So we are loading
a 1.2 icd (the common infrastructure for loading OpenCL platforms) and then
finding a 1.1 OpenCL device.
Does the /usr/local/cuda/lib64 dir also contain OpenCL.so? Where in your path
are you expecting to load the NVidia 1.1 OpenCL runtime from.
Try taking the AMD dirs out of the path (I am loathed to say this as an AMD
employee ;) ). You should be able to relying soley on the OpenCL runtime from
NVidia.
Gary
Original comment by frost.g...@gmail.com
on 20 Sep 2013 at 4:01
There is not an OpenCL.so anywhere on either computer. there is a libOpenCL.so
on my (working computer) in /usr/lib but not anywhere else in the
LD_LIBRARY_PATH. On the server (not working computer) I changed the
LD_LIBRARY_PATH to only include one location of libOpenCl.so at /usr/lib/nvidia
and it still gives me the same error.
Original comment by eelsswim...@gmail.com
on 20 Sep 2013 at 6:54
Sorry I meant libOpenCL.so. I hope (and assume) that the libOpenCL.so is
compatible with your device.
So try adding the path to libOpenCL.so to your java.library.path using
something like
java
-Djava.library.path=${PATH_TO_APARAPI_DIR_CONTAINING_SO}:${PATH_TO_LIBOPENCL_SO}
classpath + class + args
Gary
Original comment by frost.g...@gmail.com
on 20 Sep 2013 at 7:07
F.Y.I., we're using CentOS 6.4 and glibc 2.12. Following your hints about
LD_LIBRARY_PATH, ldd showed that it was glibc mismatched version,
libaparapi_x86_64.so requires glibc 2.14. We upgraded to 2.14 and fixed the
problem. Thank you for your help.
Original comment by eelsswim...@gmail.com
on 20 Sep 2013 at 8:55
Great. I am glad we sorted that.
And thanks for reporting back.
I never thought of glibc causing this. I get to learn something new every day
:)
I will close this issue.
Original comment by frost.g...@gmail.com
on 20 Sep 2013 at 9:40
Original issue reported on code.google.com by
eelsswim...@gmail.com
on 20 Sep 2013 at 3:18