On Mon, Jan 23, 2017 at 07:05:14PM +0100, Holger Levsen wrote:
> Source: ck
> Version: 0.5.2-2
> Severity: serious
> Justification: ftbfs
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
>
> Dear Maintainer,
>
> ck fails to build from source in unstable and testing on i386:
>
>
> In file included from /usr/include/limits.h:25:0,
> from
> /usr/lib/gcc/i686-linux-gnu/6/include-fixed/limits.h:168,
> from
> /usr/lib/gcc/i686-linux-gnu/6/include-fixed/syslimits.h:7,
> from /usr/lib/gcc/i686-linux-gnu/6/include-fixed/limits.h:34,
> from /build/1st/ck-0.5.2/include/ck_limits.h:47,
> from /build/1st/ck-0.5.2/include/spinlock/anderson.h:31,
> from /build/1st/ck-0.5.2/include/ck_spinlock.h:30,
> from /build/1st/ck-0.5.2/include/ck_barrier.h:31,
> from /build/1st/ck-0.5.2/src/ck_barrier_combining.c:28:
> /usr/include/features.h:364:25: fatal error: sys/cdefs.h: No such file or
> directory
> # include <sys/cdefs.h>
> ^
> compilation terminated.
>...
This is caused by "-m64 -D__x86_64__" in the gcc commandline,
which is clearly wrong on i386.
This in turn is related to:
Detecting machine architecture...success [x86_64]
Which is caused by configure using "uname -m" to determine the
target architecture - ouch.
> cheers,
> Holger
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
