Here's a (previous) explanation for the naming of dynamic libraries by the same Debian developer:
"Usually a library (lets take libfoobar as an example) comes with three files: libfoobar.so.1.234 (the actual file) libfoobar.so.1 -> libfoobar.so.1.234 (symbolic link) libfoobar.so -> libfoobar.so.1 (symbolic link) The libfoobar.so link is only needed at compilation time (when you use gcc ... -lfoobar), therefore in Debian based systems usually shipped in a libfoobar-dev package together with the headers. At compilation/linking a dependency of 'libfoobar.so.1' (this is the SONAME of the library) is recorded in the application. When the application is being executed, all the recorded dependency libraries will be loaded, e.g. libfoobar.so.1 The actual library file name can contain some additional versioning information, e.g. the next release of libfoobar could use libfoobar.so.1.567 (with an adjusted libfoobar.so.1 link) while still being compatible to the current one. An incompatible change (removal of a function, change of some struct in the library interface, ... but not just the addition of new function interfaces) would require a SONAME change. For more details see e.g. http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html Unfortunately vendors of proprietary software often don't care about naming their libraries properly and using appropriate SONAMEs :-( E.g. libcudart.so.2 does dlopen("libcuda.so") which should better have been libcuda.so.1 - otherwise this indicates: there will never be a future update that is not backwards compatible." http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2011-June/005971.html I think this makes sense, but I'm not a developer. Cheers Michael Am Mo 06 Okt 2014 00:52:32 CEST schrieb Roman Lebedev <lebedev...@gmail.com>: > See the threads "Ubuntu Gnome 14.04 - NVidia 331 - OpenCL broken > (using Darktable)", "Can't get OpenCL working" in this list. > > It works fine in AMD case, so i do not think so. > > On Mon, Oct 6, 2014 at 12:44 AM, Michael Below <be...@judiz.de> wrote: > > > Am So 05 Okt 2014 21:27:49 CEST > > schrieb Michael Below <be...@judiz.de>: > > > > > Update: Thanks to > > > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1311362/comments/7 > > > I installed nvidia-cuda-toolkit, now it works... > > > > Second update: I filed this as Debian bug #764146. Now Debian > > developer Andreas Beckmann points out that this solution works > > because it provides a symbolic link from libOpenCL.so to > > libOpenCL.so.1, he says: > > > > "darktable needs to dlopen(libOpenCL.so.1) not dlopen(libOpenCL.so)" > > > > What do you think? > > > > Thanks > > Michael > > > > > > > Thanks > > > Michael > > > > > > > > > > > > Am So 05 Okt 2014 20:39:12 CEST > > > schrieb Michael Below <be...@judiz.de>: > > > > > > > Hi, > > > > > > > > I am trying to use darktable with OpenCL with my NVidia GTX750, > > > > using Debian testing, kernel 3.16 and the NVidia driver 340.32. > > > > > > > > According to clinfo, two OpenCL platforms are there. According > > > > to darktable, libOpenCL is not found. In fact, libOpenCL.so.1 > > > > is there, as well as the necessary nvidia opencl library. > > > > > > > > Any ideas? What are the requirements for darktable to recognize > > > > an OpenCL platform? May darktable be confused because the CPU > > > > is also offered as an OpenCL platform? > > > > > > > > Thanks for your input... > > > > > > > > Michael > > > > > > > > ##### > > > > > > > > $ darktable -d opencl > > > > [opencl_init] opencl related configuration options: > > > > [opencl_init] > > > > [opencl_init] opencl: 1 > > > > [opencl_init] opencl_library: '' > > > > [opencl_init] opencl_memory_requirement: 768 > > > > [opencl_init] opencl_memory_headroom: 300 > > > > [opencl_init] opencl_device_priority: '*/!0,*/*/*' > > > > [opencl_init] opencl_size_roundup: 16 > > > > [opencl_init] opencl_async_pixelpipe: 0 > > > > [opencl_init] opencl_synch_cache: 0 > > > > [opencl_init] opencl_number_event_handles: 25 > > > > [opencl_init] opencl_micro_nap: 1000 > > > > [opencl_init] opencl_use_pinned_memory: 0 > > > > [opencl_init] opencl_use_cpu_devices: 0 > > > > [opencl_init] opencl_avoid_atomics: 0 > > > > [opencl_init] opencl_omit_whitebalance: 0 > > > > [opencl_init] > > > > [opencl_init] trying to load opencl library: '<system default>' > > > > [opencl_init] could not find opencl runtime library 'libOpenCL' > > > > [opencl_init] no working opencl library found. Continue with > > > > opencl disabled > > > > [opencl_init] FINALLY: opencl is NOT AVAILABLE on this system. > > > > [opencl_init] initial status of opencl enabled flag is OFF. > > > > > > > > ##### > > > > > > > > $ clinfo > > > > Number of platforms: 2 > > > > Platform Profile: FULL_PROFILE > > > > Platform Version: OpenCL 1.2 > > > > AMD-APP (937.2) Platform Name: > > > > AMD Accelerated Parallel Processing Platform > > > > Vendor: Advanced Micro Devices, > > > > Inc. Platform Extensions: cl_khr_icd > > > > cl_amd_event_callback cl_amd_offline_devices Platform > > > > Profile: FULL_PROFILE Platform > > > > Version: OpenCL 1.1 CUDA 6.5.14 > > > > Platform Name: NVIDIA CUDA > > > > Platform Vendor: NVIDIA > > > > Corporation Platform Extensions: > > > > cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing > > > > cl_nv_compiler_options cl_nv_device_attribute_query > > > > cl_nv_pragma_unroll > > > > > > > > > > > > Platform Name: AMD Accelerated > > > > Parallel Processing Number of > > > > devices: 1 Device > > > > Type: CL_DEVICE_TYPE_CPU > > > > Device ID: 4098 Max compute > > > > units: 4 Max work items > > > > dimensions: 3 Max work > > > > items[0]: 1024 Max work > > > > items[1]: 1024 Max work > > > > items[2]: 1024 Max work group > > > > size: 1024 Preferred vector width > > > > char: 16 Preferred vector width > > > > short: 8 Preferred vector width > > > > int: 4 Preferred vector width > > > > long: 2 Preferred vector width > > > > float: 4 Preferred vector width > > > > double: 0 Native vector width > > > > char: 16 Native vector width > > > > short: 8 Native vector width > > > > int: 4 Native vector width > > > > long: 2 Native vector width > > > > float: 4 Native vector width > > > > double: 0 Max clock > > > > frequency: 2600Mhz Address > > > > bits: 64 Max memory > > > > allocation: 2147483648 Image > > > > support: Yes Max number of > > > > images read arguments: 128 Max number of images write > > > > arguments: 8 Max image 2D width: > > > > 8192 Max image 2D height: 8192 > > > > Max image 3D width: 2048 > > > > Max image 3D height: 2048 > > > > Max image 3D depth: 2048 > > > > Max samplers within kernel: 16 > > > > Max size of kernel argument: 4096 > > > > Alignment (bits) of base address: 1024 > > > > Minimum alignment (bytes) for any datatype: 128 > > > > Single precision floating point capability > > > > Denorms: Yes > > > > Quiet NaNs: Yes > > > > Round to nearest even: Yes > > > > Round to zero: Yes > > > > Round to +ve and infinity: Yes > > > > IEEE754-2008 fused multiply-add: Yes > > > > Cache type: Read/Write > > > > Cache line size: 64 > > > > Cache size: 65536 > > > > Global memory size: 6257696768 > > > > Constant buffer size: 65536 > > > > Max number of constant args: 8 > > > > Local memory type: Global > > > > Local memory size: 32768 > > > > Error correction support: 0 > > > > Unified memory for Host and Device: 1 > > > > Profiling timer resolution: 1 > > > > Device endianess: Little > > > > Available: Yes > > > > Compiler available: Yes > > > > Execution capabilities: > > > > Execute OpenCL kernels: Yes > > > > Execute native function: Yes > > > > Queue properties: > > > > Out-of-Order: No > > > > Profiling : Yes > > > > Platform ID: 0x7f6d2d2930c0 > > > > Name: AMD Phenom(tm) > > > > II X4 810 Processor Vendor: > > > > AuthenticAMD Device OpenCL C version: > > > > OpenCL C 1.2 Driver version: 2.0 > > > > (sse2) Profile: > > > > FULL_PROFILE Version: > > > > OpenCL 1.2 AMD-APP (937.2) > > > > Extensions: cl_khr_fp64 > > > > cl_amd_fp64 cl_khr_global_int32_base_atomics > > > > cl_khr_global_int32_extended_atomics > > > > cl_khr_local_int32_base_atomics > > > > cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics > > > > cl_khr_int64_extended_atomics cl_khr_byte_addressable_store > > > > cl_khr_gl_sharing cl_ext_device_fission > > > > cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf > > > > cl_amd_media_ops cl_amd_popcnt > > > > > > > > > > > > Platform Name: NVIDIA CUDA > > > > Number of devices: 1 > > > > Device Type: > > > > CL_DEVICE_TYPE_GPU Device > > > > ID: 4318 Max compute > > > > units: 5 Max work items > > > > dimensions: 3 Max work > > > > items[0]: 1024 Max work > > > > items[1]: 1024 Max work > > > > items[2]: 64 Max work group > > > > size: 1024 Preferred vector width > > > > char: 1 Preferred vector width > > > > short: 1 Preferred vector width > > > > int: 1 Preferred vector width > > > > long: 1 Preferred vector width > > > > float: 1 Preferred vector width > > > > double: 1 Native vector width > > > > char: 1 Native vector width > > > > short: 1 Native vector width > > > > int: 1 Native vector width > > > > long: 1 Native vector width > > > > float: 1 Native vector width > > > > double: 1 Max clock > > > > frequency: 1084Mhz Address > > > > bits: 32 Max memory > > > > allocation: 536690688 Image > > > > support: Yes Max number of > > > > images read arguments: 256 Max number of images write > > > > arguments: 16 Max image 2D > > > > width: 32768 Max image 2D > > > > height: 32768 Max image 3D > > > > width: 4096 Max image 3D > > > > height: 4096 Max image 3D > > > > depth: 4096 Max samplers within > > > > kernel: 32 Max size of kernel > > > > argument: 4352 Alignment (bits) of base > > > > address: 4096 Minimum alignment (bytes) for any > > > > datatype: 128 Single precision floating point capability > > > > Denorms: Yes > > > > Quiet NaNs: Yes > > > > Round to nearest even: Yes > > > > Round to zero: Yes > > > > Round to +ve and infinity: Yes > > > > IEEE754-2008 fused multiply-add: Yes > > > > Cache type: Read/Write > > > > Cache line size: 128 > > > > Cache size: 81920 > > > > Global memory size: 2146762752 > > > > Constant buffer size: 65536 > > > > Max number of constant args: 9 > > > > Local memory type: Local > > > > Local memory size: 49151 > > > > Error correction support: 0 > > > > Unified memory for Host and Device: 0 > > > > Profiling timer resolution: 1000 > > > > Device endianess: Little > > > > Available: Yes > > > > Compiler available: Yes > > > > Execution capabilities: > > > > Execute OpenCL kernels: Yes > > > > Execute native function: No > > > > Queue properties: > > > > Out-of-Order: Yes > > > > Profiling : Yes > > > > Platform ID: 0xe31050 > > > > Name: GeForce GTX > > > > 750 Ti Vendor: NVIDIA > > > > Corporation Device OpenCL C version: > > > > OpenCL C 1.1 Driver version: > > > > 340.32 Profile: > > > > FULL_PROFILE Version: > > > > OpenCL 1.1 CUDA Extensions: > > > > cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing > > > > cl_nv_compiler_options cl_nv_device_attribute_query > > > > cl_nv_pragma_unroll cl_khr_global_int32_base_atomics > > > > cl_khr_global_int32_extended_atomics > > > > cl_khr_local_int32_base_atomics > > > > cl_khr_local_int32_extended_atomics cl_khr_fp64 > > > > > > > > ##### > > > > > > > > $ locate libOpenCL > > > > /usr/lib/x86_64-linux-gnu/libOpenCL.so.1 > > > > /usr/lib/x86_64-linux-gnu/libOpenCL.so.1.0.0 > > > > > > > > > > > > ##### > > > > > > > > $ ls -l /usr/lib/x86_64-linux-gnu/libOpenCL.so* > > > > lrwxrwxrwx 1 root root 18 Sep 1 > > > > 16:57 /usr/lib/x86_64-linux-gnu/libOpenCL.so.1 -> > > > > libOpenCL.so.1.0.0 -rw-r--r-- 1 root root 39304 Sep 1 > > > > 16:57 /usr/lib/x86_64-linux-gnu/libOpenCL.so.1.0.0 > > > > > > > > ##### > > > > > > > > $ ls -l /etc/OpenCL/vendors/ > > > > insgesamt 8 > > > > -rw-r--r-- 1 root root 15 Nov 8 2011 amdocl64.icd > > > > -rw-r--r-- 1 root root 22 Aug 6 04:58 nvidia.icd > > > > > > > > ##### > > > > > > > > $ cat /etc/OpenCL/vendors/nvidia.icd > > > > libnvidia-opencl.so.1 > > > > > > > > ##### > > > > > > > > $ locate libnvidia-opencl.so > > > > /usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.1 > > > > /usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.340.32 > > > > > > > > ##### > > > > > > > > $ ls -l /usr/lib/x86_64-linux-gnu/libnvidia-opencl.so* > > > > lrwxrwxrwx 1 root root 26 Aug 18 > > > > 11:31 /usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.1 -> > > > > libnvidia-opencl.so.340.32 -rw-r--r-- 1 root root 14085968 Aug > > > > 6 05:46 /usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.340.32 > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > > > > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS > > > > Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download > > > > White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with > > > > EventLog Analyzer > > > > > > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > > > > _______________________________________________ Darktable-users > > > > mailing list Darktable-users@lists.sourceforge.net > > > > https://lists.sourceforge.net/lists/listinfo/darktable-users > > > > > > > > > > > > > > > > -- > > Michael Below > > Rechtsanwalt > > www.judiz.de > > > > > > ------------------------------------------------------------------------------ > > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS > > Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download > > White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with > > EventLog Analyzer > > > > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > > _______________________________________________ > > Darktable-users mailing list > > Darktable-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/darktable-users > > -- Michael Below Rechtsanwalt www.judiz.de ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Darktable-users mailing list Darktable-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-users
