[Pkg-opencl-devel] [Pkg-fglrx-devel] Bug#695884: amd potentially improper OpenCL dependencies

Vincent Danjean vdanjean.ml at free.fr
Sat Sep 14 20:01:21 UTC 2013


Le 05/09/2013 11:49, Patrick Matthäi a écrit :
> Am 25.01.2013 15:51, schrieb Andreas Beckmann:
>> On 2013-01-25 12:32, Patrick Matthäi wrote:
>>> Am 24.01.2013 04:01, schrieb Bob Bib:
>>>
>>>> OK, then we should also probably replace the change
>>>> made in experimental fglrx-driver/1:13.1-1
>>>> for "amd-clinfo" & "amd-libopencl1":
>>>> Recommends: amd-opencl-icd
>>>>    with following:
>>>> Recommends: amd-opencl-icd | opencl-icd
>>>
>>> ACK, or are there any different opinions?
>>
>> half-ACK, waiting for a response from Vincent.
>>
>> AnBe
>>
> 
> Hi Vincent,
> 
> anything new from your side?

  Hi,

  Sorry to be so long.  I just checked (by creating fake packages): such
kind of relationships does not work with multiarch. More exactly, here,
the dependency will be ok as soon as a icd is installed, whatever its
architecture is...

  So, my current idea is that we need to handle virtual packages by
architecture (ie instead of libopencl1 we will have libopencl1-amd64,
libopencl1-i386, ... and so on for all our virtual packages)
If we go this path, we will need some kind of dh_ocl helper so that
we will be able to have (for example):

Package: appli-opencl
Architecture: any
Recommends: ${ocl-icd:Recommends}

that will generate the correct opencl-icd-amd64 or opencl-icd-i386 or ...
depending on the architecture currently used to compile the application.


  What do you think of that?
  Perhaps, it would be better to raise this issue (virtual packages and
multiarch) on d-d in order to get better advices?

  Regards,
    Vincent



More information about the Pkg-opencl-devel mailing list