>>> Unpacking ttmkfdir-3.0.9.tar.bz2 to /var/tmp/portage/ttmkfdir-3.0.9/work * Applying ttmkfdir-3.0.9-gcc33.patch... [ ok ] >>> Source unpacked. libtool --mode=compile g++ -Wall -pedantic -I/usr/include/freetype2 -O2 -pipe -o ttmkfdir.o -c ttmkfdir.cpp cat: CVS/Root: No such file or directory libtool: unknown option character `-' in: --mode=compile Usage: libtool -static [-] file [...] [-filelist listfile[,dirname]] [-arch_only arch] [-sacLT] Usage: libtool -dynamic [-] file [...] [-filelist listfile[,dirname]] [-arch_only arch] [-o output] [-install_name name] [-compatibility_version #] [-current_version #] [-seg1addr 0x#] [-segs_read_only_addr 0x#] [-segs_read_write_addr 0x#] [-seg_addr_table <filename>] [-seg_addr_table_filename <file_system_path>] [-all_load] [-noall_load] make: *** [ttmkfdir.o] Error 1 !!! ERROR: x11-misc/ttmkfdir-3.0.9 failed. !!! Function src_compile, Line 30, Exitcode 2 !!! (no error message) !!! If you need support, post the topmost build error, NOT this status message.
I also see this on a Linux x86 system. My guess is that this may be related to the version of libtool. I have 1.5.2 installed. I've removed the "libtool --mode=XXX" stuff from the Makefile and this allowed the compile to proceed. I don't see a good reason for having the libtool calls in there anyway, so perhaps a patch to remove them would be a good idea.
This unfortunately depends on a newer (Gentoo-enhanced) version of flex than is provided on osx. (flex-2.5.4a-r5) Nothing we can do until Apple bumps the flex version, until pathspec is completed, or if the ttmkfdir maintainers decide they don't need -r5. Will ask about this.
(In reply to comment #2) > This unfortunately depends on a newer (Gentoo-enhanced) version of flex than is provided on osx. (flex-2.5.4a-r5) Nothing we can do until Apple bumps the flex version, until pathspec is completed, or if the ttmkfdir maintainers decide they don't need -r5. Will ask about this. This fails because of libtool, not flex. It should use glibtool, not libtool
Try it in prefix.
