This is the mail archive of the
glibc-bugs@sources.redhat.com
mailing list for the glibc project.
[Bug nptl/839] New: Two "make check" failures with glibc-2.3.5
- From: "rankincj at yahoo dot com" <sourceware-bugzilla at sources dot redhat dot com>
- To: glibc-bugs at sources dot redhat dot com
- Date: 10 Apr 2005 22:38:51 -0000
- Subject: [Bug nptl/839] New: Two "make check" failures with glibc-2.3.5
- Reply-to: sourceware-bugzilla at sources dot redhat dot com
nptl/tst-cancel17.out:
going to cancel tf in-time
going to cancel tf2 in-time
in-time cancellation succeeded
aio_cancel failed
going to cancel tf early
tf cleanup handler not called
nptl/tst-cancelx17.out:
going to cancel tf in-time
going to cancel tf2 in-time
in-time cancellation succeeded
aio_cancel failed
going to cancel tf early
tf cleanup handler not called
configure options:
$ /usr/src/glibc-2.3.5/configure --prefix=/usr --with-headers=/home/chris/linu
x-2.6.11/include --with-tls --with-__thread --enable-kernel=2.6.10 --enable-add-
ons --without-gd --without-selinux --without-cvs
## --------- ##
## Platform. ##
## --------- ##
hostname = twopit
uname -m = i686
uname -r = 2.6.11.7
uname -s = Linux
uname -v = #2 SMP Sun Apr 10 20:56:37 BST 2005
GCC C compiler:
Reading specs from /usr/lib/gcc/i686-pc-linux-gnu/3.4.3/specs
Configured with: /usr/src/gcc-3.4.3/configure --prefix=/usr --enable-languages=c
,c++ --enable-version-specific-runtime-libs --enable-threads=posix --with-gnu-bi
nutils --with-system-zlib --enable-shared --enable-nls
Thread model: posix
gcc version 3.4.3
--
Summary: Two "make check" failures with glibc-2.3.5
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: nptl
AssignedTo: drepper at redhat dot com
ReportedBy: rankincj at yahoo dot com
CC: glibc-bugs at sources dot redhat dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://sources.redhat.com/bugzilla/show_bug.cgi?id=839
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.