From: Stefan Weil <sw@weilnetz.de>
To: cygwin@cygwin.com
Subject: [BUG] Package mingw64-x86_64-icu is broken
Date: Wed, 06 Jun 2018 19:13:00 -0000 [thread overview]
Message-ID: <df0243df-ca15-408b-a277-f0af7174d4c0@weilnetz.de> (raw)
Both mingw64-x86_64-icu-57.1-1 and mingw64-x86_64-icu-57.1-2 are broken:
This code always fails:
icu::Normalizer2::getInstance(nullptr, "nfkc", UNORM2_COMPOSE, error_code);
The problem was detected when comparing Tesseract for Windows
executables: while the 32 bit version worked fine, the 64 bit version
failed. The failure could be localized, and the mingw64-x86_64-icu
package was identified to be causing it.
https://github.com/tesseract-ocr/tesseract/issues/1625#issuecomment-395161152
contains details and also a short test code which can be used to
reproduce the problem.
The 32 bit package mingw64-i686-icu-57.1-2 works fine.
Kind regards
Stefan Weil
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2018-06-06 19:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 19:13 Stefan Weil [this message]
2018-06-18 12:20 ` Stefan Weil
2018-06-19 21:21 ` JonY
2018-06-19 23:46 ` Stefan Weil
2018-06-20 18:10 ` JonY
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=df0243df-ca15-408b-a277-f0af7174d4c0@weilnetz.de \
--to=sw@weilnetz.de \
--cc=cygwin@cygwin.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).