Hello Andreas, On Sun, Jun 5, 2011 at 9:07 PM, Andreas Kloeckner <[email protected]> wrote: > Also, the linking process seems to have baked some "@rpath" thing into > the executable. Not sure where we're asking it to do that.
@rpath is the path of install_path of libcurand.dylib: $ otool -D /usr/local/cuda/lib/libcurand.dylib /usr/local/cuda/lib/libcurand.dylib: @rpath/libcurand.dylib which basically means 'take library from this exact path' and was introduced in 10.5 (http://www.dribin.org/dave/blog/archives/2009/11/15/rpath/). Strangely, libcuda.dylib has explicit install_path: $ otool -D /usr/local/cuda/lib/libcuda.dylib /usr/local/cuda/lib/libcuda.dylib: /usr/local/cuda/lib/libcuda.dylib As far as I understand, while building the extension we should pass '-rpath' option to ld pointing to '/usr/local/cuda/lib'. I tried to do this (by adding "-Xlinker-rpath'/usr/local/cuda/lib'" to LDFLAGS), but it did not help. I do not have time to investigate this further right now, but will have another try in a couple of days, in case we do not find any real Mac gurus. Best regards, Bogdan _______________________________________________ PyCUDA mailing list [email protected] http://lists.tiker.net/listinfo/pycuda
