From: Andreas Jaeger <aj@suse.de>
To: Roland McGrath <roland@redhat.com>
Cc: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: glibc make check fails...
Date: Mon, 30 Sep 2002 10:03:00 -0000 [thread overview]
Message-ID: <u83crrs93t.fsf@gromit.moeb> (raw)
In-Reply-To: <u8lm5js9nd.fsf@gromit.moeb> (Andreas Jaeger's message of "Mon, 30 Sep 2002 18:51:50 +0200")
Just for the record since make was fast:
make check passes everything (except the known regex12 failure) on my
dual athlon configured with:
/cvs/libc/configure --disable-profile --enable-add-ons --prefix=/builds/test-install --enable-kernel=2.4.18
So, this leaves as only known problem the buggy --with-tls option,
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2002-09-30 17:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 3:26 Andreas Jaeger
2002-09-29 3:54 ` Roland McGrath
2002-09-29 4:20 ` Roland McGrath
2002-09-29 6:23 ` Andreas Jaeger
2002-09-29 14:46 ` Roland McGrath
2002-09-30 9:51 ` Andreas Jaeger
2002-09-30 10:03 ` Andreas Jaeger [this message]
2002-09-29 10:43 ` Ulrich Drepper
2002-09-29 14:44 ` Roland McGrath
2002-09-29 15:00 ` Ulrich Drepper
2002-09-29 15:05 ` Roland McGrath
2002-09-29 11:14 ` Ulrich Drepper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u83crrs93t.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).