jmn@power.berkeley.edu (J. Mark Noworolski) (03/12/91)
3-11-91 Getting a compleat tex system up and running for the compleat idiot. (If you use this... use it WITH the other README and manual files RTFM applies here!) I have just completed getting LaTeX/TeX compiled, installed and running on my system. This process took me about 2 weeks, but most of that was because of stupid mistakes. In principle it's really quite well documented. What I write here is intended as a guide of caveat's and suggestions. Thanks to all those who took time to answer my stupid questions and help guide me along the way. Especially karl@cs.umb.edu, and kabal@vox.inrs-telecom.uquebec.ca. Peter Kabal sent me a file similar to the one you're reading now. My Machine: decstation 3100, Ultrix4.1, gcc1.39 (I figure cc will also work, but rumours claim that bibtex won't compile under it) What I got working... TeX3.1 from labrea.stanford.edu /pub/tex/unix3.0/TeX* dvips547 xfig expo.lcs.mit.edu transfig2.1.1 svax.cs.cornell.edu (applying the patches on this one is a little messy) xdvi expo.lcs.mit.edu Notes on Compiling TeX3.1....................................... Rumour has it that this version is shipped with an old version of web2c... so after unpacking the above tar file you should get: web2c5.8a.tar.Z and web-5.8a.tar from ics.uci.edu Untar these so that they replace the old files in the web and web2c directories. (Note!!!! If you have previously attempted making tex do a 'make veryclean'!!! If you don't do this, web2c may end up using bogus files, and you will get very bizarre errors during your make). Next you should change into the tex and mf subdirectories and apply the patches there (bigtex.diff and bigmf.diff). These will enlarge your memory space from 64K to 260K or so (check out the diff's for the exact figures). If any of your users plan on including figures in their documents (ie. using any significant amount of memory) this patch is a must! On my machine site.h had to define ANSI, otherwise sprintf would be redeclared for web2c. Other differences in my site.h from site.h-dist: define BSD HAVE_GETWD, #define SPRINTF_RETURN_TYPE char * #undef _POSIX_SOURCE (not to mention the obvious directories TEXFONTS, MFBASES, etc.) Changes to the Makefile: wlibs=$(x11lib) SHELL=/bin/sh5 (since in ultrix /bin/sh is broken) (and other more obvious ones) If you can't figure out how to make your make use /bin/sh5 instead of /bin/sh you will need to change the if statements for the install target: eg: if test ! -d $(bindir); then mkdir $(bindir); else : ;fi If you try to do an install the reason for this should become quite apparent (/bin/sh sometimes returns a bad error code on an if). Next 'make all'. Then make install. I made the format and bases files by hand from the README instructions. I think the Makefile is a little overzealous in what it expects you to install. One thing about the README documentation- they claim to make a cmmf. The docs for dvips547 claim that you should _not_ have one. I listened to those with dvips. Things seem to work fine with that in mind (at least the automatic font generation via dvips does). Another item.. A recent posting by karl@cs.umb.edu (I think) suggest the use of a standard file of mf modes called modes.mf. I have used that instead of the U_wash.mf file distributed with tex3.1. ---------------------------------- xfig, and xdvi compile without major complications The patches for transfig need a little coaxing. ---------------------------------- dvips547 Make sure you print out the manual (the postscript version). Immensely useful!! For a laserwriter the mode is CanonCX, and the resolution is 300 dpi. MakeTeXPK will need to be modified to reflect this. I also recommend using /bin/sh5 to run MakeTeXPK instead of /bin/sh. I also needed to add the line: GFFONTS=$TEMPDIR; export GFFONTS after cd $TEMPDIR Presumably you can avoid this by setting up your default font search paths more intelligently than I did (in mf). Don't forget to change config.ps to reflect your printer resolution. Now when you run dvips it should automatically generate all of your pk fonts.. Run it on couple of files, and you'll have the most common pk files automatically generated! ------------------------------ good luck, (I hope this helps someone) mark -- "There's a really fine line between clever and stupid" Nigel- Lead Guitar (Spinal Tap) jmn@united.berkeley.edu, or jmn@power.berkeley.edu
klute@tommy.informatik.uni-dortmund.de (Rainer Klute) (03/13/91)
In article <jmn.668732550@power.Berkeley.EDU>, jmn@power.berkeley.edu (J. Mark Noworolski) writes: |> xfig expo.lcs.mit.edu |> xdvi expo.lcs.mit.edu Please note that since a few days the official MIT X consortium FTP is no longer expo.lcs.mit.edu but export.lcs.mit.edu. -- Dipl.-Inform. Rainer Klute klute@irb.informatik.uni-dortmund.de Univ. Dortmund, IRB klute@unido.uucp, klute@unido.bitnet Postfach 500500 |)|/ Tel.: +49 231 755-4663 D-4600 Dortmund 50 |\|\ Fax : +49 231 755-2386