Bug#788217: RFS: clfft/2.4-1 [ITP Bug#783084] -- OpenCL FFT library

[Ghislain Vaillant <ghisvail@gmail.com>]

Hi Fred,

2015-06-17 20:24 GMT+01:00 Ghislain Vaillant <ghisvail@gmail.com>:

 

> One option would be to just patch the build system and comment out the part where the offending build flag is set. I
> doubt however that upstream would be happy with this solution, since they must have setup their CI infrastructure
> around this option I presume.

> I am wondering what would be a good solution to suggest upstream about. I guess it is just more convenient for them to
> let the build system handle mutliarch builds, including setting the appropriate build flags and arch-dependent install paths
> instead of setting a proper build environment up like dh does.

I do not know what is the recommended way in cmake for this kind of "multi-arch" things.

maybe someone with more cmake experience can tell how to deal with this kind of problem.

Cheers

Fred

From what I read, other packages just patch the build system to avoid setting the m32 / m64 flags explicitly.

I'll update both clBLAS and clFFT with this change and report back.

Ghis

I have updated both clBLAS and clFFT with a patch that suppresses the offending flags.

You can build the most recent version of the package from the d-science repositories with:

  gbp buildpackage --git-upstream-tag=v2.4 --git-upstream-branch=master \
    --git-debian-branch=debian/sid --git-no-pristine-tar

for both.

Please let me know if that addresses your issues.

Ghis