From: "Matthias Klein" <matthias.klein@optimeas.de>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: [ptxdist] Qt5 and iconv: QIconvCodec::convertToUnicode: using Latin-1 for conversion, iconv_open failed
Date: Wed, 04 Nov 2015 14:59:05 +0000 [thread overview]
Message-ID: <emf4462e1d-8f7f-45b3-b6da-04fedaddde85@nb-mak> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1189 bytes --]
Hello,
every qt5 (console programm) which I compile against qt5 from the latest
ptxdist version showes the following messages at start: (but then starts
/ runs)
QIconvCodec::convertToUnicode: using Latin-1 for conversion, iconv_open
failed
QIconvCodec::convertFromUnicode: using Latin-1 for conversion,
iconv_open failed
The libc contains the iconv functions:
/opt/OSELAS.Toolchain-2014.12.1/arm-cortexa8-linux-gnueabihf/gcc-4.9.2-glibc-2.20-binutils-2.24-kernel-3.16-sanitized/bin/arm-cortexa8-linux-gnueabihf-nm
~/bsp/platform-tx53-3.12-rt/root-debug/lib/libc-2.20.so | grep iconv
00016c18 T iconv
00016d54 T iconv_close
00016a90 T iconv_open
There are also modules in the rootfs
ls -l /usr/lib/gconv/
-rwxr-xr-x 1 root root 5504 Nov 4 12:46 ISO8859-1.so
-rwxr-xr-x 1 root root 9600 Nov 4 12:46 ISO8859-15.so
-rw-r--r-- 1 root root 56284 Nov 4 12:46 gconv-modules
The same console application did run without these messages when
building against qt4.
(The qt5 build (and the qt4 build in the past) is without GUI)
Does anyone has a tip whats the reason for these messages?
Best regards,
Matthias
[-- Attachment #1.2: Type: text/html, Size: 2347 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2015-11-04 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 14:59 Matthias Klein [this message]
2015-11-06 11:39 ` Michael Olbrich
2015-11-09 8:16 ` Matthias Klein
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=emf4462e1d-8f7f-45b3-b6da-04fedaddde85@nb-mak \
--to=matthias.klein@optimeas.de \
--cc=ptxdist@pengutronix.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