Source: klibc
Version: 2.0.4-2
Severity: important
The following thing can happen if the system used to build
src:klibc has ccache installed but the system libklibc-dev
is installed and used doesn’t:
root@ara4:~ # echo 'main() { return 0; }' >x.c; klcc -c x.c
open3: exec of /usr/lib/ccache/gcc -D__KLIBC__=2 -D__KLIBC_MINOR__=0
-D_BITSIZE=32 -fno-stack-protector -fwrapv -nostdinc -iwithprefix include
-D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=32
-I/usr/lib/klibc/include/m68k-linux-gnu -I/usr/lib/klibc/include/arch/m68k
-I/usr/lib/klibc/include/bits32 -I/usr/lib/klibc/include -Os
-fomit-frame-pointer -c -x c x.c failed at /usr/bin/klcc line 148.
For this reason, I propose that debian/rules MUST fail the
build ('exit 1') if ccache is installed. Additionally, put
a Build-Conflicts on ccache into debian/rules, maybe.
@Adrian: please remove ccache from your buildds as this is
not the only problem with it (e.g. toolchain upgrades when
the user does not manually clean the cache will fail).
I’ve scanned the current src:klibc build logs; it seems to
me that only the m68k binary packages are affected. We can
schedule a binNMU for that, once ccache is gone from *all*
buildds for that architecture, or I do a porter upload.
-- System Information:
Debian Release: 8.0
APT prefers unreleased
APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: m68k
Kernel: Linux 3.16.0-4-m68k
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
