Your message dated Sun, 25 Aug 2019 08:17:04 +0200
with message-id <[email protected]>
and subject line Re: Bug#892428: pocl: FTBFS on x32: tries to build
kernel/host/ for amd64
has caused the Debian Bug report #892428,
regarding pocl: FTBFS on x32: tries to build kernel/host/ for amd64
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
892428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892428
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: pocl
Version: 1.0-2
Severity: normal
User: [email protected]
Usertags: x32
Builds of pocl for x32 (admittedly not a release architecture) have
been failing, as detailed at [1]:
cd "/<<PKGBUILDDIR>>/obj-x86_64-linux-gnux32/lib/kernel/host" &&
/usr/bin/clang-4.0 --target=x86_64-pc-linux-gnu -D_CL_DISABLE_HALF
-march=x86-64 -emit-llvm -ffp-contract=off -xc -D__CBUILD__
-fno-stack-protector -fno-PIC -DDORENAME -DVEC128 -I
"/<<PKGBUILDDIR>>/lib/kernel/sleef/arch" -I
"/<<PKGBUILDDIR>>/lib/kernel/sleef/libm" -I
"/<<PKGBUILDDIR>>/lib/kernel/sleef/include" -O1 -o
"/<<PKGBUILDDIR>>/obj-x86_64-linux-gnux32/lib/kernel/host/x86-64/v128_sleefsimddp.c.bc"
-c "/<<PKGBUILDDIR>>/lib/kernel/sleef/libm/sleefsimddp.c"
In file included from /<<PKGBUILDDIR>>/lib/kernel/sleef/libm/sleefsimddp.c:8:
In file included from
/usr/lib/llvm-4.0/bin/../lib/clang/4.0.1/include/stdint.h:61:
/usr/include/stdint.h:26:10: fatal error: 'bits/libc-header-start.h' file not
found
Could you please take a look? (Note the explicit inappropriate
-march=x86-64.)
Thanks!
[1]
https://buildd.debian.org/status/fetch.php?pkg=pocl&arch=x32&ver=1.1%7Erc2-1&stamp=1520368921&raw=0
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/[email protected]
--- End Message ---
--- Begin Message ---
Version: 1.1-3
On Sat, 10 Mar 2018 00:35:31 +0100 Andreas Beckmann <[email protected]> wrote:
> From the 1.1~rc2-1 buildlog:
> ...
> -- llvm-config's LLVM_HOST_TARGET is: x86_64-pc-linux-gnu
> ...
> /usr/bin/clang-4.0 --target=x86_64-pc-linux-gnu -D_CL_DISABLE_HALF
> -march=x86-64 ...
> ...
>
> The LLVM_HOST_TARGET setting comes from llvm-config-4.0 --host-target:
>
> cmake/LLVM.cmake:
> run_llvm_config(LLVM_HOST_TARGET --host-target)
>
> which seems to return a wrong value on x32.
> Due to lack of a x32 porterbox I cannot test this myself.
>From the 1.1-7 buildlog:
...
-- llvm-config's LLVM_HOST_TARGET is: x86_64-pc-linux-gnux32
...
/usr/lib/llvm-6.0/bin/clang-6.0 --target=x86_64-pc-linux-gnux32
-D_CL_DISABLE_HALF -march=...
...
So this was fixed in llvm 5.0 or 6.0
Andreas
--- End Message ---
