/bin/sh ./libtool --tag=CC --mode=compile x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -O2 -pipe -march=native -Wall -Wall -I.. -I./.. -c -o rfc2047.lo rfc2047.c libtool: compile: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -O2 -pipe -march=native -Wall -Wall -I.. -I./.. -c rfc2047.c -fPIC -DPIC -o .libs/rfc2047.o rfc2047.c:379:30: error: unknown type name ‘unicode_char’ static int encode_word(const unicode_char *uc, ^~~~~~~~~~~~ rfc2047.c:412:31: error: unknown type name ‘unicode_char’ ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_20170706-204158 ------------------------------------------------------------------- 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 482040 [details] emerge-info.txt
Created attachment 482042 [details] emerge-history.txt
Created attachment 482044 [details] environment
Created attachment 482046 [details] etc.portage.tbz2
Created attachment 482048 [details] logs.tbz2
Created attachment 482050 [details] net-mail:courier-imap-4.17.3:20170708-134522.log
Created attachment 482052 [details] temp.tbz2
I think this is a dependency issue: courier-imap-4.7.13 cannot be built against courier-unicode-2.0 because of the "unknown type name ‘unicode_char’" error. If courier-unicode is downgraded to 1.4 the build succeeds. But the latest courier-authlib requires courier-unicode-2.0 so it is necessary to downgrade courier-authlib as well. As a temporary workaround the following masks in /etc/portage/package.mask may be tried: =net-libs/courier-unicode-2.0 =net-libs/courier-authlib-0.68.0-r1 =net-libs/courier-authlib-0.68.0 and you can then hopefully emerge these package versions: net-libs/courier-unicode-1.4 net-libs/courier-authlib-0.67.0 net-mail/courier-imap-4.17.3 This may or may not work ... I suppose there can be problems if you have more packages that depend on courier-unicode.
(In reply to Rabbe Fogelholm from comment #8) > I think this is a dependency issue: courier-imap-4.7.13 cannot be built > against courier-unicode-2.0 because of the "unknown type name > ‘unicode_char’" error. If courier-unicode is downgraded to 1.4 the build > succeeds. But the latest courier-authlib requires courier-unicode-2.0 so it > is necessary to downgrade courier-authlib as well. > > As a temporary workaround the following masks in /etc/portage/package.mask > may be tried: > > =net-libs/courier-unicode-2.0 > =net-libs/courier-authlib-0.68.0-r1 > =net-libs/courier-authlib-0.68.0 > > and you can then hopefully emerge these package versions: > > net-libs/courier-unicode-1.4 > net-libs/courier-authlib-0.67.0 > net-mail/courier-imap-4.17.3 > > This may or may not work ... I suppose there can be problems if you have > more packages that depend on courier-unicode. This worked for me, maybe the next version or something?
this is fixed or rather will not happen with courier-imap-4.18.0. both courier-unicode-2.0 and courier-imap-4.18.0 released on 23 june 2017. have to be tied in deps. the fix is the matter of updating courier-imap.
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3bcf1b2baf345cdfa1519186ec9fef6f1cca61d3
