[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#629518: Preliminary AMD APP SDK Packaging



Dnia 2011-06-15, śro o godzinie 02:50 +0200, Andreas Beckmann pisze:
> On 2011-06-10 16:21, Tomasz Rybak wrote:
> > Dnia 2011-06-08, śro o godzinie 18:15 +0200, Andreas Beckmann pisze:
> >> I have prepared and use local packages for the AMD APP SDK and offer to
> >> package this for Debian once someone confirmed that it can be put into
> >> non-free.
> > 
> > Can you put packaging information (i.e. debian/ directory) on some
> > repository? I would like to try to build packages myself and test
> > building PyOpenCL with them.
> 
> Vcs-Svn: svn://svn.debian.org/svn/pkg-nvidia/packages/amd-app-sdk/trunk
> Vcs-Browser:
> http://anonscm.debian.org/viewvc/pkg-nvidia/packages/amd-app-sdk/
> 
> Have fun! Comments welcome.

Thanks.
I was able to build it offline (only 64-bit versions, as I did
not have 32-bit libraries installed).

Currently amd-app-sdk-dev does not build. Will it be just meta-package
depending on all AMD APP-related packages?

lintian complains about:
W: amd-libopencl1: package-name-doesnt-match-sonames libOpenCL1
At the same time I was not able to install amd-libopencl1:
Zaznaczenie poprzednio niezaznaczonego pakietu amd-libopencl1.
dpkg: w odniesieniu do amd-libopencl1_2.4-0_amd64.deb zawierającego
amd-libopencl1:
 amd-libopencl1 w konflikcie z libopencl1
  nvidia-libopencl1 dostarcza libopencl1 i jest obecny oraz
zainstalowany.
dpkg: błąd przetwarzania amd-libopencl1_2.4-0_amd64.deb (--install):
 konflikt pakietów - nie będzie instalowany amd-libopencl1

Translation - both nvidia-libopencl1 and amd-libopencl1 provide
libopencl1 and as nvidia-libopencl1 is properly installed
dpkg will not install amd-libopencl1.


But thanks to having /usr/lib/libamdocl64.so in amd-opencl-icd
python-pyopencl was able to detect and use OpenCL implementations
from both NVIDIA and AMD. So current situation makes sense
and works for my packages.
By current situation I mean nvidia-opencl-icd providing
opencl-icd and depending on nvidia-libopencl1, and amd-opencl-icd
providing opencl-icd and containing AMD OpenCL implementation.
As long as I can install more than one ICD and all of them work
I am content.

Would it make sense to have similar meta-package for opencl-dev?
This way if I have NVIDIA hardware I install nvidia-opencl-dev
(providing, say, opencl-dev), and if I have AMD/ATI hardware
I install amd-opencl-dev (or amd-app-sdk) which also can provide
opencl-dev meta-package. If not I guess I can build-depend
python-pyopencl on "nvidia-opencl-dev | amd-app-sdk-dev".

In summary:
package works, thanks for providing it.

Best regards.

-- 
Tomasz Rybak <bogomips@post.pl> GPG/PGP key ID: 2AD5 9860
Fingerprint A481 824E 7DD3 9C0E C40A  488E C654 FB33 2AD5 9860
http://member.acm.org/~tomaszrybak

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: