From: Steven Munroe <munroesj@us.ibm.com>
To: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: [PATCH] localedata/tst-sscanf should use internal test locales
Date: Wed, 07 Mar 2007 20:54:00 -0000 [thread overview]
Message-ID: <45EF2A13.2020205@us.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 267 bytes --]
The new test ./localedata/tst-sscanf.s attempts to set locale fa_IR.
this locale is not built internal to glibc for make check (fa_IR.UTF-8
is) and the LOCPATH is not set.
This patch sets tst-sscanf-ENV in the Makefile and changes tst-sscanf.c
to use fa_IR.UTF-8.
[-- Attachment #2: libc-tst-sscanf-20070307.txt --]
[-- Type: text/plain, Size: 1134 bytes --]
2007-03-07 Steven Munroe <sjmunroe@us.ibm.com>
* localedata/Makefile: Define tst-sscanf-ENV
* localedata/tst-sscanf.c: Use fa_IR.UTF-8 which exists internally.
diff -urN libc25-cvstip-20070307/localedata/Makefile libc25/localedata/Makefile
--- libc25-cvstip-20070307/localedata/Makefile 2007-02-18 22:40:43.000000000 -0600
+++ libc25/localedata/Makefile 2007-03-07 14:28:56.630826704 -0600
@@ -289,6 +289,8 @@
bug-iconv-trans-ENV = LOCPATH=$(common-objpfx)localedata
+tst-sscanf-ENV = LOCPATH=$(common-objpfx)localedata
+
tst-leaks-ENV = MALLOC_TRACE=$(objpfx)tst-leaks.mtrace \
LOCPATH=$(common-objpfx)localedata
$(objpfx)mtrace-tst-leaks: $(objpfx)tst-leaks.out
diff -urN libc25-cvstip-20070307/localedata/tst-sscanf.c libc25/localedata/tst-sscanf.c
--- libc25-cvstip-20070307/localedata/tst-sscanf.c 2007-02-18 22:40:13.000000000 -0600
+++ libc25/localedata/tst-sscanf.c 2007-03-07 14:29:13.047861688 -0600
@@ -36,7 +36,7 @@
static int
do_test (void)
{
- if (setlocale (LC_ALL, "fa_IR") == NULL)
+ if (setlocale (LC_ALL, "fa_IR.UTF-8") == NULL)
{
puts ("cannot set fa_IR locale");
return 1;
next reply other threads:[~2007-03-07 20:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 20:54 Steven Munroe [this message]
2007-03-14 22: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=45EF2A13.2020205@us.ibm.com \
--to=munroesj@us.ibm.com \
--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).