[Pkg-opencl-devel] Bug#759943: libclc: FTBFS: /bin/sh: 1: clang: not found

[Lucas Nussbaum]

Source: libclc
Version: 0~git20140101-1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20140830 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/«PKGBUILDDIR»'
> LLVM-CC nvptx--nvidiacl/lib/synchronization/barrier.cl.bc
> clang -MMD -MF nvptx--nvidiacl/lib/synchronization/barrier.cl.bc.d -target nvptx--nvidiacl -I`dirname ./ptx-nvidiacl/lib/synchronization/barrier.cl` -I./generic/include -fno-builtin -Dcl_clang_storage_class_specifiers -Dcl_khr_fp64 -Dcles_khr_int64 -D__CLC_INTERNAL -emit-llvm -c -o nvptx--nvidiacl/lib/synchronization/barrier.cl.bc ./ptx-nvidiacl/lib/synchronization/barrier.cl
> LLVM-CC nvptx--nvidiacl/lib/workitem/get_group_id.cl.bc
> clang -MMD -MF nvptx--nvidiacl/lib/workitem/get_group_id.cl.bc.d -target nvptx--nvidiacl -I`dirname ./ptx-nvidiacl/lib/workitem/get_group_id.cl` -I./generic/include -fno-builtin -Dcl_clang_storage_class_specifiers -Dcl_khr_fp64 -Dcles_khr_int64 -D__CLC_INTERNAL -emit-llvm -c -o nvptx--nvidiacl/lib/workitem/get_group_id.cl.bc ./ptx-nvidiacl/lib/workitem/get_group_id.cl
> /bin/sh: 1: clang: not found
> LLVM-CC nvptx--nvidiacl/lib/workitem/get_local_id.cl.bc
> make[1]: *** [nvptx--nvidiacl/lib/synchronization/barrier.cl.bc] Error 127

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/08/30/libclc_0~git20140101-1_unstable.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. The build
was done with DEB_BUILD_OPTIONS="parallel=4", so if your packaging tries
to support this, it might be a good idea to explore whether this might
be the cause of the failure.