From: Andreas Jaeger <aj@suse.de>
To: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Fix debug testcases
Date: Fri, 15 Jul 2005 09:58:00 -0000 [thread overview]
Message-ID: <m34qawmlvt.fsf@gromit.moeb> (raw)
[-- Attachment #1: Type: text/plain, Size: 1545 bytes --]
Running the glibc CVS testsuite I noticed that a number of the debug
tests failed. The problem was the the de_DE.UTF-8 locale was not
found. We should pass it - as we do in other tests - via the
environment. The appended patch let's me pass all tests.
Ok to commit?
Andreas
2005-07-15 Andreas Jaeger <aj@suse.de>
* debug/Makefile (tst-lfschk3-ENV): New, set locale.
(tst-lfschk2-ENV): New.
(tst-lfschk1-ENV): New.
(tst-chk3-ENV): New.
(tst-chk2-ENV): New.
(tst-chk1-ENV): New.
============================================================
Index: debug/Makefile
--- debug/Makefile 13 Jul 2005 06:09:13 -0000 1.27
+++ debug/Makefile 15 Jul 2005 09:56:49 -0000
@@ -54,6 +54,13 @@ CFLAGS-pread64_chk.c = -fexceptions -fas
CFLAGS-recv_chk.c = -fexceptions -fasynchronous-unwind-tables
CFLAGS-recvfrom_chk.c = -fexceptions -fasynchronous-unwind-tables
+tst-chk1-ENV = LOCPATH=$(common-objpfx)localedata
+tst-chk2-ENV = LOCPATH=$(common-objpfx)localedata
+tst-chk3-ENV = LOCPATH=$(common-objpfx)localedata
+tst-lfschk1-ENV = LOCPATH=$(common-objpfx)localedata
+tst-lfschk2-ENV = LOCPATH=$(common-objpfx)localedata
+tst-lfschk3-ENV = LOCPATH=$(common-objpfx)localedata
+
tests = backtrace-tst tst-chk1 tst-chk2 tst-chk3 \
tst-lfschk1 tst-lfschk2 tst-lfschk3 test-strcpy_chk test-stpcpy_chk
--
Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next reply other threads:[~2005-07-15 9:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-15 9:58 Andreas Jaeger [this message]
2005-07-15 10:34 ` 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=m34qawmlvt.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=libc-hacker@sources.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).