ttmkfdir-3.0.9-r3 will not build. Reproducible: Always Steps to Reproduce: 1. sudo emerge ttmkfdir 2. 3. Actual Results: lsiden@morpheus ~ $ sudo emerge ttmkfdir Calculating dependencies ...done! >>> emerge (1 of 1) x11-misc/ttmkfdir-3.0.9-r3 to / >>> md5 files ;-) ttmkfdir-3.0.9-r2.ebuild >>> md5 files ;-) ttmkfdir-3.0.9-r3.ebuild >>> md5 files ;-) files/ttmkfdir-2.0-gentoo.patch >>> md5 files ;-) files/ttmkfdir-3.0.9-cpp.patch >>> md5 files ;-) files/digest-ttmkfdir-3.0.9-r2 >>> md5 files ;-) files/digest-ttmkfdir-3.0.9-r3 >>> md5 files ;-) files/ttmkfdir-3.0.9-gcc34.patch >>> md5 files ;-) files/ttmkfdir-3.0.9-freetype_new_includes.patch >>> md5 files ;-) files/ttmkfdir2-ignore-FIRSTINDEX.patch >>> md5 files ;-) files/ttmkfdir-3.0.9-encoding.patch >>> md5 files ;-) files/ttmkfdir-1.0-gentoo.diff >>> md5 files ;-) files/ttmkfdir-3.0.9-zlib.patch >>> md5 files ;-) files/ttmkfdir-3.0.9-gcc33.patch >>> md5 src_uri ;-) ttmkfdir-3.0.9.tar.bz2 >>> Unpacking source... >>> Unpacking ttmkfdir-3.0.9.tar.bz2 to /var/tmp/portage/ttmkfdir-3.0.9-r3/work * Applying ttmkfdir-3.0.9-cpp.patch ... [ ok ] * Applying ttmkfdir-3.0.9-zlib.patch ... [ ok ] * Applying ttmkfdir-3.0.9-gcc34.patch ... [ ok ] * Applying ttmkfdir-3.0.9-encoding.patch ... [ ok ] * Applying ttmkfdir-3.0.9-freetype_new_includes.patch ... [ ok ]>>> Source unpacked. libtool --mode=compile i686-pc-linux-gnu-g++ -Wall -pedantic -I/usr/include/freetype2 -march=athlon-xp -pipe -o ttmkfdir.o -c ttmkfdir.cpp cat: CVS/Root: No such file or directory libtool: compile: unable to infer tagged configuration libtool: compile: specify a tag with `--tag' make: *** [ttmkfdir.o] Error 1 !!! ERROR: x11-misc/ttmkfdir-3.0.9-r3 failed. Expected Results: run to completion I worked around this by masking this ebuild in /etc/portage/package.mask.
You neglected to post emerge --info output, as instructed to when filing the bug.
Created attachment 68837 [details] emerge.info
Attached output of "emerge --info" as per request.
Remove the stale libtool version: emerge -C sys-devel/libtool-1.4.3-r4 *** This bug has been marked as a duplicate of 67692 ***