On Mon, 6 Oct 2014 12:26:05 +0200 "Michael Below" <be...@judiz.de> wrote:
> 2. And darktable doesn’t use the correct SONAME when it tries to load > libOpenCL.so instead of libOpenCL.so.1. This works only if > nvidia-cuda-toolkit (or, probably, any other OpenCL development package) is > installed, which provides the symlink from libOpenCL.so to libOpenCL.so.1. Opening libOpenCL.so is standart-de-facto, everyone does it. I couldn't find any official specification of which SONAME is canonical. If libOpenCL.so.1 should be used (and not libOpenCL.so.0 or libOpenCL.so.2) instead - where is that defined as correct? My point is that changing our code this way will fix this Debian issue, but might break some other setups. IMHO Debian should get over itself and consider libOpenCL as a special case - there are many vendors that provide this library and AFAIK no written rules how to do it. Compromise would be to try opening both these names, that might be a good idea, but will require a bit more changes to the code. ------------------------------------------------------------------------------ Slashdot TV. Videos for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk _______________________________________________ Darktable-users mailing list Darktable-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-users
