When I tried to emerge media-sound/lilypond I got errors about "-- -" being an invalid option to t1asm during the font generation part of the compile (sorry, I didn't save the output). "equery belongs t1asm" got two results for /usr/bin/t1asm: app-text/t1utils-1.28 and media-libs/freetype-1.3.1-r3. It appears that the actual version was 1.2, presumably from freetype. I re-emerged t1utils, verified that it was indeed a new version (1.28) and then successfully emerged lilypond. Would it maybe be better to have freetype depend on t1utils? Reproducible: Always Steps to Reproduce: 1.emerge t1utils 2.emerge freetype 3.emerge lilypond Actual Results: Compile fails during font building with errors from t1asm Expected Results: Lilypond compiles and builds fonts successfully. ACCEPT_KEYWORDS="~x86"
*** Bug 61108 has been marked as a duplicate of this bug. ***
Fixed in CVS. (Don't install t1asm and getafm from freetype-1) Thanks for the bug report. I didn't add t1utils to freetype's RDEPEND, because t1asm is in freetype1-contrib and seems optional.