[Pkg-opencl-devel] Bug#892428: pocl: FTBFS on x32: tries to build kernel/host/ for amd64

[Aaron M. Ucko]

Good question.  Copying the LLVM maintainers accordingly.

-- Aaron

Andreas Beckmann <anbe at debian.org> writes:

> On 2018-03-09 03:55, Aaron M. Ucko wrote:
>> 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.)
>
> So what is the correct setting for x32 here? I think already
> --target=x86_64-pc-linux-gnu is wrong ... (and that one gets
> autodetected, not overridden by me)
>
> I need to pass an -march or similar option since pocl does not know
> about the "use the compilers default" concept (and does the equivalent
> of -march=native by default)
>
> Andreas