/bin/sh ./libtool --mode=compile x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I/var/tmp/portage/media-libs/libid3tag-0.15.1b-r4/work/libid3tag-0.15.1b -I. -Wall -pipe -march=native -O2 -fomit-frame-pointer -c -o compat.lo /var/tmp/portage/media-libs/libid3tag-0.15.1b-r4/work/libid3tag-0.15.1b/compat.c x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I/var/tmp/portage/media-libs/libid3tag-0.15.1b-r4/work/libid3tag-0.15.1b -I. -Wall -pipe -march=native -O2 -fomit-frame-pointer -c /var/tmp/portage/media-libs/libid3tag-0.15.1b-r4/work/libid3tag-0.15.1b/compat.c -fPIC -DPIC -o .libs/compat.o compat.gperf:116:1: error: conflicting types for 'id3_compat_lookup' In file included from compat.gperf:37:0: /var/tmp/portage/media-libs/libid3tag-0.15.1b-r4/work/libid3tag-0.15.1b/compat.h:36:26: note: previous declaration of 'id3_compat_lookup' was here struct id3_compat const *id3_compat_lookup(register char const *, ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: gnome_20170525-085524 ------------------------------------------------------------------- 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) [3] pypy3 (fallback) [4] jython2.7 (fallback) Available Ruby profiles: [1] ruby21 (with Rubygems) [2] ruby22 (with Rubygems) * java-config: The following VMs are available for generation-2: 1) IcedTea JDK 7.2.6.10 [icedtea-bin-7] *) IcedTea JDK 3.4.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-7 [2] icedtea-bin-8 system-vm
Created attachment 475878 [details] emerge-info.txt
Created attachment 475880 [details] config.log.tbz2
Created attachment 475882 [details] emerge-history.txt
Created attachment 475884 [details] environment
Created attachment 475886 [details] etc.portage.tbz2
Created attachment 475888 [details] media-libs:libid3tag-0.15.1b-r4:20170610-024611.log
Created attachment 475890 [details] temp.tbz2
*** This bug has been marked as a duplicate of bug 605158 ***