-- Performing Test ICONV_HAVE_WERROR - Success -- Performing Test ICONV_SECOND_ARGUMENT_IS_CONST -- Performing Test ICONV_SECOND_ARGUMENT_IS_CONST - Failed -- Found Iconv: /usr/lib/libc.so -- Looking for dgettext -- Looking for dgettext - found ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-no-multilib_20170716-132601 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.3.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby21 (with Rubygems) * [2] ruby22 (with Rubygems)
Created attachment 485308 [details] emerge-info.txt
Created attachment 485310 [details] emerge-history.txt
Created attachment 485312 [details] environment
Created attachment 485314 [details] etc.portage.tbz2
Created attachment 485316 [details] logs.tbz2
Created attachment 485318 [details] net-misc:tigervnc-1.8.0:20170717-071802.log
Created attachment 485320 [details] temp.tbz2
Thank you for your report. It seems to me that there is no problem. This is because tigervnc don't use iconv.
This appears to be a duplicate of bug 599958 based on their very similar build logs, so when this bug was filed Toralf attributed the build failure to a configure issue that upstream seems to believe is harmless (https://github.com/TigerVNC/tigervnc/issues/719#issuecomment-423477929). Oh well. *** This bug has been marked as a duplicate of bug 599958 ***
