Source: llvm-toolchain-7
Version: 1:7~+rc3-3
Severity: normal
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: powerpcspe

Hello!

The build of llvm-toolchan-7 (and 6.0) fails on powerpcspe because the
compiled clang compiler cannot find any header files when being invoked
during build [1] (here from 6.0):

[100%] Built target clang
make[3]: Leaving directory '/<<PKGBUILDDIR>>/build-llvm'
/usr/bin/cmake -E cmake_progress_start /<<PKGBUILDDIR>>/build-llvm/CMakeFiles 0
make[2]: Leaving directory '/<<PKGBUILDDIR>>/build-llvm'
cd build-llvm \
CFLAGS=`dpkg-buildflags --get CFLAGS`; \
CFLAGS="$CFLAGS `dpkg-buildflags --get CPPFLAGS`"; \
echo $CFLAGS; \
bin/clang++ -c $CFLAGS -std=c++11 ../compiler-rt/lib/fuzzer/*.cpp -IFuzzer; \
ar ruv libFuzzer.a Fuzzer*.o
-g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
In file included from ../compiler-rt/lib/fuzzer/FuzzerClangCounters.cpp:22:
In file included from ../compiler-rt/lib/fuzzer/FuzzerDefs.h:15:
In file included from 
/usr/lib/gcc/powerpc-linux-gnuspe/8/../../../../include/c++/8/cassert:43:
In file included from 
/usr/lib/gcc/powerpc-linux-gnuspe/8/../../../../include/powerpc-linux-gnuspe/c++/8/bits/c++config.h:508:
In file included from 
/usr/lib/gcc/powerpc-linux-gnuspe/8/../../../../include/powerpc-linux-gnuspe/c++/8/bits/os_defines.h:39:
/usr/include/features.h:424:12: fatal error: 'sys/cdefs.h' file not found
#  include <sys/cdefs.h>
           ^~~~~~~~~~~~~
1 error generated.

The patch turned out to be trivial and can be found in [2].

It needs to be applied in both 6.0 and 7.

Thanks,
Adrian

> [1] 
> https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-6.0&arch=powerpcspe&ver=1%3A6.0.1-7&stamp=1536742371&raw=0
> [2] https://reviews.llvm.org/D52066

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Reply via email to