Bug#840725: [Pkg-opencl-devel] Bug#840840: pocl: Does not build on several architectures
You shouldn't need libpoclu-dev to build OpenCL-using code, only ocl-icd-opencl-dev (which is available on all architectures). What does require an ICD is _running_ OpenCL code, including in the test suite (if any); as buildds are unlikely to have a GPU, build-time OpenCL-using tests can only be run on architectures with pocl-opencl-icd. You could build but not test the OpenCL-using part on the other architectures, but you may well not want to. There isn't a standard for how to turn off OpenCL (beyond the conventions applying to compile-time-optional features in general): check the git log for how you turned it on, and/or upstream's documentation.
Bug#840725: Bug#840840: pocl: Does not build on several architectures
On Sat, Oct 15, 2016 at 08:39:08PM +0200, Andreas Beckmann wrote: > > So if the fact remains that pocl does not build anywhere else than on > > intel I need to restrict the set of architectures for libhmsbeagle as > > well. > > Or just restrict the use of OpenCL to the architectures that have pocl? I'd like to do that - but how? I have no idea about all these things. Any hint? Kind regards Andreas. -- http://fam-tille.de
Bug#840725: Bug#840840: pocl: Does not build on several architectures
On Sat, Oct 15, 2016 at 08:39:08PM +0200, Andreas Beckmann wrote: > On 2016-10-15 19:57, Andreas Tille wrote: > > because libpoclu-dev is not available on most architectures. Since > > libhmsbeagle has build on all those architectures either the set of > > Build-Depends has changed (may be together with khronos-opencl-clhpp?) > > or there was a point in time when pocl has build on more architectures > > than currently. > > The outdated libhmsbeagle binary packages are from 2.1.2+20150609-1.1, > predating the use of libpoclu-dev (since 2.1.2+20151220-1). > So libhmsbeagle never built successfully with libpoclu-dev on more > architectures than currently (i.e. only on amd64). > > While theoretically pocl could be available on all architectures (that > support CPUs), that doesn't work right now and I don't know if anyone is > working on fixing this. > > > So if the fact remains that pocl does not build anywhere else than on > > intel I need to restrict the set of architectures for libhmsbeagle as > > well. > > Or just restrict the use of OpenCL to the architectures that have pocl? > > Andreas > -- http://fam-tille.de
Bug#840840: pocl: Does not build on several architectures
On 2016-10-15 19:57, Andreas Tille wrote: > because libpoclu-dev is not available on most architectures. Since > libhmsbeagle has build on all those architectures either the set of > Build-Depends has changed (may be together with khronos-opencl-clhpp?) > or there was a point in time when pocl has build on more architectures > than currently. The outdated libhmsbeagle binary packages are from 2.1.2+20150609-1.1, predating the use of libpoclu-dev (since 2.1.2+20151220-1). So libhmsbeagle never built successfully with libpoclu-dev on more architectures than currently (i.e. only on amd64). While theoretically pocl could be available on all architectures (that support CPUs), that doesn't work right now and I don't know if anyone is working on fixing this. > So if the fact remains that pocl does not build anywhere else than on > intel I need to restrict the set of architectures for libhmsbeagle as > well. Or just restrict the use of OpenCL to the architectures that have pocl? Andreas
Bug#840725: Bug#840840: pocl: Does not build on several architectures
On Sat, Oct 15, 2016 at 04:27:45PM +0200, Andreas Beckmann wrote: > On 2016-10-15 16:09, Andreas Tille wrote: > > > >https://buildd.debian.org/status/package.php?p=pocl > > Right, pocl FTBFS everywhere except linux-i386/amd64, and always has > (with maybe some spurious successes when tests were not being run). > Everything outdated on the release architectures has been decrufted. > > Or did you want to file a *wishlist* bug to support more architectures? > FTBFS on an architecture where it has not been built before (i.e. no > outdated binary packages in the archive that would prevent testing > migration) is not RC. Well, the thing is that bug #840725 of libhmsbeagle was reopened[1] because libpoclu-dev is not available on most architectures. Since libhmsbeagle has build on all those architectures either the set of Build-Depends has changed (may be together with khronos-opencl-clhpp?) or there was a point in time when pocl has build on more architectures than currently. So if the fact remains that pocl does not build anywhere else than on intel I need to restrict the set of architectures for libhmsbeagle as well. Kind regards Andreas. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840725;msg=22 -- http://fam-tille.de
Bug#840840: pocl: Does not build on several architectures
On 2016-10-15 16:09, Andreas Tille wrote: > Hi Andreas, > > On Sat, Oct 15, 2016 at 03:59:16PM +0200, Andreas Beckmann wrote: >> Huh? The only architecture with outdated binaries is powerpcspe (which >> only "successfully" built them in the past thanks to a nocheck buildd). >> Feel free to get them decrufted as well. > > What about > >arm64: > https://buildd.debian.org/status/fetch.php?pkg=pocl=arm64=0.13-8=1476101601 >armhf: > https://buildd.debian.org/status/fetch.php?pkg=pocl=armhf=0.13-8=1476101525 >mips: > https://buildd.debian.org/status/fetch.php?pkg=pocl=mips=0.13-8=1476107564 > > and all those others listed here > >https://buildd.debian.org/status/package.php?p=pocl Right, pocl FTBFS everywhere except linux-i386/amd64, and always has (with maybe some spurious successes when tests were not being run). Everything outdated on the release architectures has been decrufted. Or did you want to file a *wishlist* bug to support more architectures? FTBFS on an architecture where it has not been built before (i.e. no outdated binary packages in the archive that would prevent testing migration) is not RC. Andreas
Bug#840840: pocl: Does not build on several architectures
Hi Andreas, On Sat, Oct 15, 2016 at 03:59:16PM +0200, Andreas Beckmann wrote: > Huh? The only architecture with outdated binaries is powerpcspe (which > only "successfully" built them in the past thanks to a nocheck buildd). > Feel free to get them decrufted as well. What about arm64: https://buildd.debian.org/status/fetch.php?pkg=pocl=arm64=0.13-8=1476101601 armhf: https://buildd.debian.org/status/fetch.php?pkg=pocl=armhf=0.13-8=1476101525 mips: https://buildd.debian.org/status/fetch.php?pkg=pocl=mips=0.13-8=1476107564 and all those others listed here https://buildd.debian.org/status/package.php?p=pocl Kind regards Andreas. -- http://fam-tille.de
Bug#840840: pocl: Does not build on several architectures
Source: pocl Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, the pocl source does not build on several architectures where it has built before. The problem seem to be failed tests. Please see: https://buildd.debian.org/status/package.php?p=pocl Kind regards and thanks for maintaining pocl Andreas. -- System Information: Debian Release: 8.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
