The end of the emerge gives me this: LaTeX Font Warning: Some font shapes were not available, defaults substituted. ) (see the transcript file for additional information) Output written on canna.dvi (223 pages, 806552 bytes). Transcript written on canna.log. dvips -f canna.dvi > canna.ps This is dvips(k) 5.92b p1.6 Copyright 2003 ASCII Corp.(www-ptex@ascii.co.jp) based on dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com) ' TeX output 2004.02.21:1909' -> kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+398/600 --dpi 998 rml mktexpk: don't know how to create bitmap font for rml. kpathsea: Appending font creation commands to missfont.log. dvips: Font rml not found, using cmr10 instead. make: *** [canna.ps] Error 139 !!! ERROR: app-i18n/canna-3.6_p4 failed. !!! Function src_compile, Line 48, Exitcode 2 !!! (no error message) Calculating dependencies ...done! >>> emerge (1 of 1) app-i18n/canna-3.6_p4 to / >>> md5 src_uri ;-) Canna36p4.tar.gz Emerging with ``env USE="-doc" emerge canna'' appears to work, but of course the documentation isn't generated. Reproducible: Always Steps to Reproduce: 1. 2. 3. # emerge info Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.2-gentoo-r1) ================================================================= System uname: 2.6.2-gentoo-r1 i686 AMD Athlon(tm) XP 1900+ Gentoo Base System version 1.4.3.13 Autoconf: sys-devel/autoconf-2.58-r1 Automake: sys-devel/automake-1.7.7 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-g -O2 -fstack-protector" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb:/usr/kde/3.2/share/config:/usr/kde/3.1/share/config:/usr/share/texmf/tex/generic/config/ /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-g -O2 -fstack-protector" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs fixpackages nostrip sandbox userpriv" GENTOO_MIRRORS="ftp://mirrors.tds.net/gentoo http://mirror.tucdemonic.org/gentoo/ ftp://gentoo.mirrors.pair.com/ http://gentoo.mirrors.pair.com/ http://gentoo.ccccom.com ftp://gentoo.ccccom.com http://gentoo.oregonstate.edu http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow X Xaw3d aalib apm arts avi berkdb canna cdr cjk crypt cups debug doc dvd encode esd foomaticdb freetype freewnn gdbm gif gnome gpm gtk gtk2 guile imlib java joystick jpeg kde libg++ libwww mad maildir matrox mbox mikmod mozilla mozsvg mpeg mule ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline ruby scanner sdl slang spell sse ssl svga tcltk tcpd tetex tiff truetype usb video_cards_matrox x86 xinerama xml2 xmms xv zlib"
Did you happen to install tetex before? We had several reports (not on bugzilla) that you need to remove tetex completely before installing ptex, otherwise you'll get an error like this bug. In such a case, ptex emerges fine but some config files will be corrupted.
I did have tetex installed; I had "emerge -C"ed it, but that apparently wasn't enough. I unmerged everything tex related, and then deleted the /usr/share/texmf directory (which wasn't completely empty), and then emerged ptex (and the rest) again, and then the canna documentation worked okay. I've changed the bug subject so it will be easier for people with problems like this to find it.
Hum, there isn't good way to solve the problem... All that we can do is to add an advisory to ptex ebuild and inform users to remove /usr/share/texmf/web2c before merging ptex. We cannot simply rm -rf that directory in case users update it manually. Any idea?
*** Bug 64186 has been marked as a duplicate of this bug. ***
This will be fixed in the next major version of tetex (tetex-3, which will be released this year) and corresponding ptex, but I'm not going to fix it in tetex-2 (at least I think so at the moment).
