[Pkg-opencl-devel] OpenCL and multiarch

[Tomasz Rybak]

Dnia 2015-02-19, czw o godzinie 00:00 +0100, Simon Richter pisze:
> Hi,
> 
> I've asked this about a year or two ago already, but dropped the ball.
> How should we deal with ICDs in a multiarch system, especially with a
> system like wine, which pulls in both i386 and amd64 ICD loaders?
> 
> The easiest approach is probably to use (e.g.)
> 
>   /etc/OpenCL/intel.i386.icd
>   /etc/OpenCL/intel.amd64.icd
> 
> with paths pointing to multiarch locations, which allows for
> co-installable packages, but requires the ICD loader to properly handle
> the error from attempting to load libraries for the wrong architecture.
> 
> If better separation is desired, we might need to poke the Khronos group.
> 

You email got me thinking about PyOpenCL.
It is still built only for amd64 and i386, as it was in the
beginning, when the only OpenCL implementation in Debian
came from NVIDIA drivers.
Do you think it would make sense to change it to Architecture: any?
On the one hand ocl-icd-libopencl1 is available on all architectures.
On the other hand, from all packages providing opencl-icd, only
mesa is available for something other than amd64/i386: armhf.

I might try enabling multi-arch for PyOpenCL when OpenCL
implementations provide it, but for now I'd like to normalize
situation with architectures.

Best regards.

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-opencl-devel/attachments/20150224/a7a05edf/attachment.sig>