Dnia 2011-05-31, wto o godzinie 16:13 +0200, Ed Lin pisze: > Package: python-pyopencl > Version: 0.92-1 > > python-pyopencl has nvidia dependencies but it actually also works on > AMD/ATI hardware as well. These "wrong" dependencies make it harder to > use with fglrx.
Can you describe how you are using OpenCL with fglrx? I have tried to find packages providing OpenCL, but was able to only find NVIDIA-related packages. I do not own ATI/AMD GPU, so I do not know how people on Debian are using it with OpenCL. > > I'm not sure about the solution, I guess there are two ways: > Remove the nvidia decencies and somehow notify the user that he needs > to be running a (non-free for now) graphic driver with opencl support. > Or: > Properly handle the dependencies so that installing the package either > fetches fglrx or nvidia* depending on the detected hardware. > Currently package depends on: libnvidia-compiler1 | libnvidia-compiler, nvidia-libopencl1, nvidia-opencl-common, Second dependency pulls OpenCL library, and third ICD file (telling OpenCL where to find available OpenCL libraries). I think it could be possible to change them to: libopencl1 opencl-icd I am not sure about first dependency (libnvidia-compiler1); I will need to experiment a bit. Then, if fglrx provides those packages, it would work without any problems. I have checked PyOpenCL with APP OpenCL on CPU and it works without any problems, so I believe dependencies are the only problem. > Related ubuntu bug: "pyopencl falsely depends on nvidia-current " > https://bugs.launchpad.net/ubuntu/+source/pyopencl/+bug/763457 > Thanks for providing link to this bug - I do not know why I have not received mail from launchpad about this bug. -- Tomasz Rybak <bogom...@post.pl> GPG/PGP key ID: 2AD5 9860 Fingerprint A481 824E 7DD3 9C0E C40A 488E C654 FB33 2AD5 9860 http://member.acm.org/~tomaszrybak
signature.asc
Description: This is a digitally signed message part
