There seems to be a bug in libcdio or the ebuilds for libcdio. It depends on the point of view. x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../lib/driver -I../include/ -O2 -march=nocona -pipe -Wall -Wchar-subscripts -Wmissing-prototypes -Wmissing-declarations -Wunused -Wpointer-arith -Wwrite-strings -Wnested-externs -Wno-sign-compare -c cddb.c cddb.c: In function `init_cddb': cddb.c:120: error: dereferencing pointer to incomplete type cddb.c:124: error: dereferencing pointer to incomplete type make[3]: *** [cddb.o] Error 1 make[3]: Leaving directory `/var/tmp/portage/libcdio-0.73/work/libcdio-0.73/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/libcdio-0.73/work/libcdio-0.73/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/libcdio-0.73/work/libcdio-0.73' make: *** [all] Error 2 !!! ERROR: dev-libs/libcdio-0.73 failed. Call stack: ebuild.sh, line 1539: Called dyn_compile ebuild.sh, line 939: Called src_compile libcdio-0.73.ebuild, line 39: Called die !!! (no error message) !!! If you need support, post the topmost build error, and the call stack if relevant. Google pointed me to a bugreport of the Linux distribution Lunar. http://foo-projects.org/pipermail/lunar-bugs/2005-July/003199.html According to the reply/comment the quick solution would be a workaround to build first libcdio, then vcdimage and then libcdio again full-featured. However this doesn't seem to work in my case. libcdio compiles fine without cddb use flag but it fails with cddb.
libcddb version?
And, why don't you try 0.77?
media-libs/libcddb-1.2.1 Sorry, that I've forgot about the versions. I tried 0.77 and it seems to work. (no compilation errors) So it looks like a upstream bug.
*** This bug has been marked as a duplicate of 131156 ***
