[Pkg-opencl-devel] Bug#768691: beignet: FTBFS in jessie: /bin/sh: 1: llvm-as-3.4: not found

[Lucas Nussbaum]

Source: beignet
Version: 0.8-1.1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20141108 qa-ftbfs
Justification: FTBFS in jessie on amd64

Hi,

During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> make[3]: Entering directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
> make[3]: Nothing to be done for 'utests/CMakeFiles/utest_generator.dir/build'.
> make[3]: Leaving directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
> /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 
> Scanning dependencies of target pch_object
> make[3]: Leaving directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
> make -f backend/src/CMakeFiles/pch_object.dir/build.make backend/src/CMakeFiles/pch_object.dir/build
> [  0%] [  0%] [  0%] make[3]: Entering directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
> /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 15
> [  0%] Generating ocl_memcpy.ll.bc
> Built target utest_generator
> Generating ocl_barrier.ll.bc
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/backend/src && rm -f ocl_barrier.ll.bc
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/backend/src && rm -f ocl_memcpy.ll.bc
> [  1%] cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/backend/src && llvm-as-3.4 -o ocl_barrier.ll.bc /«PKGBUILDDIR»/backend/src/ocl_barrier.ll
> Generating ocl_memset.ll.bc
> /bin/sh: 1: llvm-as-3.4: not found
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/backend/src && llvm-as-3.4 -o ocl_memcpy.ll.bc /«PKGBUILDDIR»/backend/src/ocl_memcpy.ll
> make[3]: *** [backend/src/ocl_barrier.ll.bc] Error 127

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/11/08/beignet_0.8-1.1_jessie.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.