[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#634152: FTBFS on kfreebsd-amd64



Package: libc0.1
Version: 2.13-10
User: debian-bsd@lists.debian.org
Usertags: kfreebsd

It's a bit strange, because the buildds didn't seem to have this problem,
but eglibc 2.13-10 fails to build on kfreebsd-amd64 due to testsuite errors.

(this is pristine eglibc 2.13-10, without any of my local changes)

I found the problem with kFreeBSD 8.2, then tried 8.1 to be sure it's not
related to kernel version and found the same problem:

#
# Testsuite failures, someone should be working towards
# fixing these! They are listed here for the purpose of
# regression testing during builds.
# Format: <Failed test>, Error <Make error code> [(ignored)]
#
annexc.out, Error 1 (ignored)
check-localplt.out, Error 1
tst-aio10.out, Error 1
tst-aio4.out, Error 1
tst-aio9.out, Error 1
tst-atime.out, Error 1
tst-longjmp_chk.out, Error 1
tst-mknodat.out, Error 1
tst-renameat.out, Error 1
tst-timer4.out, Error 1
tst-waitid.out, Error 1
tst-writev.out, Error 1
***************
Encountered regressions that don't match expected failures:
tst-atime.out, Error 1
make: *** [/home/rmh/eglibc/test/eglibc-2.13/stamp-dir/check_libc] Error 1

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: kfreebsd-amd64 (x86_64)

Kernel: kFreeBSD 8.1-1-amd64
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libc0.1 depends on:
ii  libc-bin                      2.13-10    Embedded GNU C Library: Binaries
ii  libgcc1                       1:4.6.1-1  GCC support library

libc0.1 recommends no packages.

Versions of packages libc0.1 suggests:
ii  debconf [debconf-2.0]         1.5.40     Debian configuration management sy
ii  glibc-doc                     2.13-10    Embedded GNU C Library: Documentat
ii  locales                       2.13-10    Embedded GNU C Library: National L

-- debconf information excluded



Reply to: