Source: intel-compute-runtime Version: 20.37.17906-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<<PKGBUILDDIR>>/build' > cd /<<PKGBUILDDIR>>/build && /usr/bin/cmake -E cmake_depends "Unix Makefiles" > /<<PKGBUILDDIR>> /<<PKGBUILDDIR>>/opencl/source/scheduler > /<<PKGBUILDDIR>>/build /<<PKGBUILDDIR>>/build/igdrcl_lib_release/scheduler > /<<PKGBUILDDIR>>/build/igdrcl_lib_release/scheduler/CMakeFiles/scheduler_Gen9core.dir/DependInfo.cmake > --color= > Scanning dependencies of target scheduler_Gen9core > make[3]: Leaving directory '/<<PKGBUILDDIR>>/build' > make -f > igdrcl_lib_release/scheduler/CMakeFiles/scheduler_Gen9core.dir/build.make > igdrcl_lib_release/scheduler/CMakeFiles/scheduler_Gen9core.dir/build > make[3]: Entering directory '/<<PKGBUILDDIR>>/build' > [ 25%] Generating ../../bin/scheduler/x64/gen9/scheduler_Gen9core.bin > cd /<<PKGBUILDDIR>>/opencl/source/scheduler && > LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/build/bin /<<PKGBUILDDIR>>/build/bin/ocloc > -q -file scheduler.cl -device skl -cl-intel-greater-than-4GB-buffer-required > -64 -out_dir /<<PKGBUILDDIR>>/build/bin/scheduler/x64/gen9 -cpp_file -options > -I/usr/include/igc\ -I/usr/include/igc/cif\ > -I/usr/include/igc/ocl_igc_shared/executable_format\ > -I/usr/include/igc/ocl_igc_shared/device_enqueue\ -I\ ../gen9\ > -cl-kernel-arg-info\ -cl-std=CL2.0\ -cl-intel-disable-a64WA > make[3]: *** > [igdrcl_lib_release/scheduler/CMakeFiles/scheduler_Gen9core.dir/build.make:84: > bin/scheduler/x64/gen9/scheduler_Gen9core.bin] Error 245 The full build log is available from: http://qa-logs.debian.net/2020/09/26/intel-compute-runtime_20.37.17906-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.
