Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 610738

Summary: net-misc/tigervnc-1.7.1: error: unmappable character
Product: Gentoo Linux Reporter: bitozoid
Component: Current packagesAssignee: otakuto.gentoo
Status: RESOLVED FIXED    
Severity: normal CC: mmokrejs, proxy-maint, tb
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description bitozoid 2017-02-23 21:51:19 UTC
Cannot compile tigervnc-1.7.1 because of errors like this:

/var/tmp/paludis/net-misc-tigervnc-1.7.1/work/tigervnc-1.7.1/java/com/tigervnc/rfb/UnicodeToKeysym.java:38: error: unmappable character for encoding ASCII
    new codepair(0x01a1, 0x0104), /*                     Aogonek ?? LATIN CAPITAL LETTER A WITH OGONEK */

It looks as a locale setting:

https://github.com/TigerVNC/tigervnc/issues/258

So I defined C.UTF-8 locale:

https://lists.gt.net/gentoo/user/321555

and then:

--- tigervnc-1.7.1.ebuild-pre   2017-02-23 21:46:39.020296295 +0000
+++ tigervnc-1.7.1.ebuild       2017-02-23 21:21:39.400909491 +0000
@@ -146,7 +146,7 @@
 }

 src_compile() {
-       cmake-utils_src_compile
+       LC_ALL=C.UTF-8 cmake-utils_src_compile

        if use server; then
                # deps of the vnc module and the module itself

That way it worked.
Comment 1 Thomas Beutin 2017-03-30 07:33:52 UTC
I run into the same problem, and this worked for me:

# LC_ALL=en_US.utf8 nice -n 19 emerge -1 net-misc/tigervnc

en_US.utf8 is defined on my system.

But IMHO the solution suggested by bitozoid@gmail.com in comment 1 should be preferred.
Comment 2 Thomas Beutin 2017-03-30 07:35:47 UTC
(In reply to Thomas Beutin from comment #1)
...
> But IMHO the solution suggested by bitozoid@gmail.com in comment 1 should be
> preferred.

Sorry, i'm talking about the solution provided in the description, not in my own comment...
Comment 3 Michael Palimaka (kensington) gentoo-dev 2017-03-30 07:44:26 UTC
We normally use just LC_ALL="C", could you please confirm it works with that too?
Comment 4 Thomas Beutin 2017-03-30 15:20:27 UTC
(In reply to Michael Palimaka (kensington) from comment #3)
> We normally use just LC_ALL="C", could you please confirm it works with that
> too?

No, it doesn't work, at least if the C.UTF-8 locale does not exists.

(We're talking about the solution outlined in the bug description, right!?)
Comment 5 Martin Mokrejš 2017-04-03 10:04:12 UTC
I hit this issue also with:

# locale
LANG=
LC_CTYPE="POSIX"
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE="POSIX"
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=
#
# grep -v "^#" /etc/locale.gen 

en_US ISO-8859-1
en_US.UTF-8 UTF-8
cs_CZ.UTF-8 UTF-8
cs_CZ ISO-8859-2
cs_CZ.CP1250 CP1250
#

[ 34%] Building CXX object common/rfb/CMakeFiles/rfb.dir/CSecurityStack.cxx.o
cd /scratch/var/tmp/portage/net-misc/tigervnc-1.7.1-r2/work/tigervnc-1.7.1/common/rfb && /usr/bin/x86_64-pc-linux-gnu-g++  -DBUILD_TIMESTAMP="\"2017-04-03 11:51\"" -DHAVE_CONFIG_H -DHAVE_GNUTLS -I/scratch/var/tmp/portage/net-misc/tigervnc-1.7.1-r2/work/tigervnc-1.7.1 -I/scratch/var/tmp/portage/net-misc/tigervnc-1.7.1-r2/work/tigervnc-1.7.1/common   -DNDEBUG -O2 -pipe -maes -mpclmul -mpopcnt -mavx -march=native -Wall -Wformat=2   -fPIC -o CMakeFiles/rfb.dir/CSecurityStack.cxx.o -c /scratch/var/tmp/portage/net-misc/tigervnc-1.7.1-r2/work/tigervnc-1.7.1/common/rfb/CSecurityStack.cxx
/scratch/var/tmp/portage/net-misc/tigervnc-1.7.1-r2/work/tigervnc-1.7.1/java/com/tigervnc/rfb/UnicodeToKeysym.java:38: error: unmappable character for encoding ASCII
    new codepair(0x01a1, 0x0104), /*                     Aogonek ?? LATIN CAPITAL LETTER A WITH OGONEK */

followed by 99 more errors like this                                                            ^

LC_ALL=en_US.utf8 emerge tigervnc

worked.
Comment 6 Thomas Beutin 2017-06-25 05:50:13 UTC
This behavoir continues in the net-misc/tigervnc-1.8.0 ebuild (see bug 614742).
Comment 7 Honza 2017-07-04 06:36:39 UTC
It worked with just LC_CTYPE for me. And yes tigervnc 1.8 is still affected.
Comment 8 Larry the Git Cow gentoo-dev 2017-12-06 12:14:19 UTC
The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2f028f5775ee892397290e2a119cfb87a6f2a041

commit 2f028f5775ee892397290e2a119cfb87a6f2a041
Author:     Takuto Yoshida <otakuto.gentoo@gmail.com>
AuthorDate: 2017-12-05 17:44:53 +0000
Commit:     Michael Palimaka <kensington@gentoo.org>
CommitDate: 2017-12-06 12:14:08 +0000

    net-misc/tigervnc: fix encoding option to utf-8, bug #634918 and #610738
    
    And bump internal xorg.
    
    Closes: https://bugs.gentoo.org/610738
    Closes: https://bugs.gentoo.org/634918
    Closes: https://github.com/gentoo/gentoo/pull/6453
    Package-Manager: Portage-2.3.16, Repoman-2.3.6

 net-misc/tigervnc/Manifest                 |   1 +
 net-misc/tigervnc/files/java-utf8.patch    |  11 ++
 net-misc/tigervnc/tigervnc-1.8.0-r1.ebuild | 190 +++++++++++++++++++++++++++++
 3 files changed, 202 insertions(+)