I am switching to texlife and texlife-latex breaks: (/var/tmp/portage/dev-texlive/texlive-latex-2007/work/texmf-dist/tex/generic/ba bel/hyphen.cfg ! I can't find file `ushyphen.tex'. <to be read again> \relax l.357 \repeat Please type another input file name: ! Emergency stop. <to be read again> \relax l.357 \repeat No pages of output. Transcript written on latex.log. Error: `pdftex -ini -jobname=latex -progname=latex -translate-file=cp227.tcx *latex.ini' failed ############################################################################### fmtutil: Error! Not all formats have been built successfully. Visit the log files in directory /var/tmp/portage/dev-texlive/texlive-latex-2007/work/texmf-var/web2c for details. ############################################################################### This is a summary of all `failed' messages and warnings: `pdftex -ini -jobname=latex -progname=latex -translate-file=cp227.tcx *latex.ini' failed ^[[31;01m*^[[0m ^[[31;01m*^[[0m ERROR: dev-texlive/texlive-latex-2007 failed. ^[[31;01m*^[[0m Call stack: ^[[31;01m*^[[0m ebuild.sh, line 1695: Called dyn_compile ^[[31;01m*^[[0m ebuild.sh, line 1033: Called qa_call 'src_compile' ^[[31;01m*^[[0m ebuild.sh, line 44: Called src_compile ^[[31;01m*^[[0m ebuild.sh, line 1377: Called texlive-module_src_compile ^[[31;01m*^[[0m texlive-module.eclass, line 53: Called die ^[[31;01m*^[[0m The specific snippet of code: ^[[31;01m*^[[0m TEXMFHOME="${S}/texmf:${S}/texmf-dist"\ ^[[31;01m*^[[0m fmtutil --cnffile "${i}" --fmtdir "${S}/texmf-var/web2c" --all\ ^[[31;01m*^[[0m || die "failed to build format ${i}" ^[[31;01m*^[[0m The die message: ^[[31;01m*^[[0m failed to build format texmf/fmtutil/format.latex.cnf ^[[31;01m*^[[0m ^[[31;01m*^[[0m If you need support, post the topmost build error, and the call stack if relevant. ^[[31;01m*^[[0m A complete build log is located at '/var/tmp/portage/dev-texlive/texlive-latex-2007/temp/build.log'. ^[[31;01m*^[[0m Currently I am trying to figure this out and where to get this file :-)
Stop hitting refresh... *** This bug has been marked as a duplicate of bug 197395 ***
