On Wed, 20 Apr 2011 16:04:21 +0000, "Means, Joel L" <[email protected]> wrote: > Hi all, > I am having an issue using PyOpenCL on a RHEL Linux system. This is a shared > server to which I don't have root access. The latest Nvidia drivers are not > installed system-wide, so I extracted the driver and placed the > libOpenCL.so.1.0.0 file in ~/opencl/lib64. I also created symlinks for > libOpenCL.so.1 and libOpenCL.so. I set > LD_LIBRARY_PATH=/home/<username>/opencl/lib64. I can set --cl-inc-dir and > --cl-lib-dir for the build and everything builds just fine. I can install it > locally, but when I try to import pyopencl, I get this error: > > ImportError: libOpenCL.so.1: cannot open shared object file: No such file or > directory > > Sure enough, when I do `ldd _cl.so`, I get this: > > libOpenCL.so.1 => not found > libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00002ba75aca2000) > libm.so.6 => /lib64/libm.so.6 (0x00002ba75afa2000) > libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00002ba75b226000) > libpthread.so.0 => /lib64/libpthread.so.0 (0x00002ba75b434000) > libc.so.6 => /lib64/libc.so.6 (0x00002ba75b64f000) > /lib64/ld-linux-x86-64.so.2 (0x0000003eb2200000) > > So, how do I get _cl.so to search my local path for libOpenCL.so.1? I > have tried setting ldflags='-rpath=/home/<username>/opencl/lib64' in > the configure script, but I just get 'unrecognized option –rpath' when > it links _cl.so. Any suggestions?
LD_LIBRARY_PATH should be the right recipe. Do _cl.so and libOpenCL.so.1
have the same bit-ness? (32/64) ("file" should tell you)
Andreas
pgpxC9jJv5VgF.pgp
Description: PGP signature
_______________________________________________ PyOpenCL mailing list [email protected] http://lists.tiker.net/listinfo/pyopencl
