from /var/tmp/portage/sci-geosciences/mapserver-7.0.5/work/mapserver-7.0.5/mapkmlrenderer.h:38, from /var/tmp/portage/sci-geosciences/mapserver-7.0.5/work/mapserver-7.0.5/mapkml.cpp:33: /usr/include/unicode/umachine.h:347:13: error: ‘char16_t’ does not name a type typedef char16_t UChar; ^ In file included from /usr/include/unicode/utypes.h:39:0, ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: desktop-gcc5_20170517-212644 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-5.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) [3] pypy3 (fallback) Available Ruby profiles: [1] ruby21 (with Rubygems) [2] ruby22 (with Rubygems) * java-config: The following VMs are available for generation-2:
Created attachment 474046 [details] emerge-info.txt
Created attachment 474048 [details] emerge-history.txt
Created attachment 474050 [details] environment
Created attachment 474052 [details] etc.portage.tbz2
Created attachment 474054 [details] sci-geosciences:mapserver-7.0.5:20170523-223113.log
Created attachment 474056 [details] temp.tbz2
I think it's fair to close this now. See https://bugs.gentoo.org/620046#c1. The gist is that the relevant GCCs have been masked for quite some time. If a user actually hits this, I guess we can revisit it, but somebody running that old of a GCC is going to face other problems on a modern Gentoo system.
