From: Roland McGrath <roland@redhat.com>
To: Thorsten Kukuk <kukuk@suse.de>
Cc: Bruno Haible <bruno@clisp.org>, Jakub Jelinek <jakub@redhat.com>,
Ulrich Drepper <drepper@redhat.com>
Cc: libc-hacker@sources.redhat.com
Subject: Re: iconv-test fails with current glibc CVS
Date: Mon, 09 Aug 2004 20:12:00 -0000 [thread overview]
Message-ID: <200408092012.i79KCRxa029818@magilla.sf.frob.com> (raw)
In-Reply-To: Thorsten Kukuk's message of Monday, 9 August 2004 15:24:05 +0200 <20040809132404.GA31442@suse.de>
> 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.
prev parent reply other threads:[~2004-08-09 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 13:28 Thorsten Kukuk
2004-08-09 20:12 ` Roland McGrath [this message]
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=200408092012.i79KCRxa029818@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=bruno@clisp.org \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=kukuk@suse.de \
/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).