2012/7/9 Gareth Hughes <[email protected]>: > On Mon, 2012-07-09 at 10:06 +0200, Peter Dyballa wrote: >> Am 09.07.2012 um 04:04 schrieb Gareth Hughes: >> >> > I thought fmtutil-local.cnf was just for customisation. >> >> Indeed! And one customisation could have been to comment XeTeX related lines >> copied from somewhere which made tlmgr remove or comment the lines in the >> generated fmtutil.cnf. >> >> I thought you would check the contents of >> /usr/local/texlive/2011/texmf-var/web2c/fmtutil.cnf to see whether XeTeX >> related formats are still mentioned there. One option is to simply run >> >> fmtutil-sys --listcfg >> >> No sudo is necessary, it's a read-only process. You can compare the output >> with that of >> >> fmtutil --listcfg > > These files look identical to me, and both have xetex and xelatex. > >> >> When they're different, then you have private FMTs and you need to run >> >> fmtutil --byengine xetex >> >> or a general >> >> fmtutil --refresh > > Both of these fail and produce errors. > This is a summary of all `failed' messages: > `pdftex -ini -jobname=eplain -progname=eplain > -translate-file=cp227.tcx *eplain.ini' failed > `pdftex -ini -jobname=jadetex -progname=jadetex *jadetex.ini' > failed > `pdftex -ini -jobname=pdfjadetex -progname=pdfjadetex > *pdfjadetex.ini' failed > `pdftex -ini -jobname=latex -progname=latex > -translate-file=cp227.tcx *latex.ini' failed > `pdftex -ini -jobname=pdflatex -progname=pdflatex > -translate-file=cp227.tcx *pdflatex.ini' failed > `pdftex -ini -jobname=mllatex -progname=mllatex > -translate-file=cp227.tcx -mltex mllatex.ini' failed > `pdftex -ini -jobname=pdftex -progname=pdftex > -translate-file=cp227.tcx *pdfetex.ini' failed > `pdftex -ini -jobname=etex -progname=etex > -translate-file=cp227.tcx *etex.ini' failed > `pdftex -ini -jobname=pdfetex -progname=pdfetex > -translate-file=cp227.tcx *pdfetex.ini' failed > `eptex -ini -jobname=eptex -progname=eptex *eptex.ini' failed > `eptex -ini -jobname=platex -progname=platex *platex.ini' > failed > `xetex -ini -jobname=xetex -progname=xetex -etex xetex.ini' > failed > `xetex -ini -jobname=xelatex -progname=xelatex -etex > xelatex.ini' failed > `pdftex -ini -jobname=xmltex -progname=xmltex *xmltex.ini' > failed > `pdftex -ini -jobname=pdfxmltex -progname=pdfxmltex > *pdfxmltex.ini' failed > > However, no log file was written in ~/.texlive2012/texmf-var/web2c . >> It is normal if your binaries are below /usr/local/texlive/2011, they know nothing about ~/texlive2012. The log files will most probably be below ~/.texlive2011
Believe me, your problems are caused by files mixed from different TL versions or by collisions of TL with linux distro's TeX. I saw it many times, fixing PATH is the first mandatory step, then verification that texmf.cnf and other config files are correct. Another source of problems may be caused by TEX* environment variables that point to incorrect files and/or directories. >> The options fmtutil or fmtutil-sys know can be found be found by running >> >> fmtutil --help >> >> -- >> Greetings >> >> Pete >> >> I hope to die before I *have* to use Microsoft Word. >> - Donald E. Knuth, 2001-10-02 in Tübingen >> >> >> >> >> -------------------------------------------------- >> Subscriptions, Archive, and List information, etc.: >> http://tug.org/mailman/listinfo/xetex > > > > > -------------------------------------------------- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex -- Zdeněk Wagner http://hroch486.icpf.cas.cz/wagner/ http://icebearsoft.euweb.cz -------------------------------------------------- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
