-------------- Original message from Derek Peschel <[email protected]>: -------------- > Though I've only been skimming this thread, I can probably help you with > your TeX problem. Sorry if I'm telling you things you already know. > I don't know much, so suggestions can sometimes get me where I want to go. ;)
<snip> > Your experiments with Cygwin created a mutant monster. :) A .fmt file > is a binary dump of TeX's data structures, so that next time TeX can read > all its data in one operation instead of running a bunch of initialization > code. You're running the DVI-generating version of etex, but the format > file was dumped by the PDF-generating version. Evidently the two versions > dump to the same pathname, and can't coexist. Can you uninstall pdfetex? > Then you'll need to regenerate the correct format file. Reinstalling etex > is probably easiest. > We'll see how well cygwin uninstalls things then. Pulling one option at a time now. > > (Fatal format file error; I'm stymied) > > /usr/bin/texi2dvi: texinfo.tex appears to be broken, quitting. > > I suspect the above line is misleading and texinfo.tex was never read. > But you may want to check that by running etex yourself. > I may have to go there eventually to figure this out, but not today. ;) > > make: *** [doc/gforth.dvi] Error 1 > > You don't want to edit the Makefile to skip the generation of gforth.dvi, > right? > The Makefile is part of the gforth build system and Anton's domain. He and Bernd have a tough problem keeping up with all the various systems. I'm just trying to go back to the cygwin platform after my Mac died and reporting the issues as I find them. > Is there a gforth.pdf target in the Makefile, and do you want to run it? > Then this problem with conflicting format files would become more serious. > The etex man page I looked up describes the TEXFORMATS environment variable > and the -fmt command-line option, so at least there are solutions. > I do have the Windows version installed that has everything pre-built. This is just my attempt to get the cygwin build working from the CVS sources. It's almost always problematic when I try a new one again, and Anton and Bernd have been very patient with me over the years. In the end, we usually come up with some tweak to their install scripts and I end up with an environment that works for some of my other experiments. However, thanks for adding your expertise to the journey. ;) DaR --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
