* iconv-test fails with current glibc CVS
@ 2004-08-09 13:28 Thorsten Kukuk
2004-08-09 20:12 ` Roland McGrath
0 siblings, 1 reply; 2+ messages in thread
From: Thorsten Kukuk @ 2004-08-09 13:28 UTC (permalink / raw)
To: libc-hacker
Hi,
with current glibc CVS, iconv-test fails with:
test data: ISO-2022-JP-3 -> UTF8 OK/OK -> ISO-2022-JP-3 OK/FAILED
does this work for somebody? How to get the full error message?
Thorsten
--
Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de
SuSE Linux AG Maxfeldstr. 5 D-90409 Nuernberg
--------------------------------------------------------------------
Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: iconv-test fails with current glibc CVS
2004-08-09 13:28 iconv-test fails with current glibc CVS Thorsten Kukuk
@ 2004-08-09 20:12 ` Roland McGrath
0 siblings, 0 replies; 2+ messages in thread
From: Roland McGrath @ 2004-08-09 20:12 UTC (permalink / raw)
To: Thorsten Kukuk; +Cc: Bruno Haible, Jakub Jelinek, Ulrich Drepper, libc-hacker
> test data: ISO-2022-JP-3 -> UTF8 OK/OK -> ISO-2022-JP-3 OK/FAILED
> does this work for somebody? How to get the full error message?
I see the same failure. There is no error message to see.
This just means that the result output didn't match
iconvdata/testdata/ISO-2022-JP-3 after converting from UTF8.
The CC'd people recently made changes to this converter and/or its test data.
Hopefully they can shed some light on the situation.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-08-09 20:12 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-08-09 13:28 iconv-test fails with current glibc CVS Thorsten Kukuk
2004-08-09 20:12 ` Roland McGrath
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).