www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1993/04/05/11:32:27

Date: Mon, 5 Apr 93 11:02:32 EDT
From: kent AT cme DOT nist DOT gov (Ernie Kent)
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Printing Texinfo docs

Some of the documentation is TeX, but other parts are
Texinfo, which is apparantly a little different. I got
a local wizard to help me get printouts. He succeeded.

I asked him to write down what he did, and this is his
reply:

>From coombs AT cme DOT nist DOT gov Wed Mar 17 16:34:52 1993
To: kent AT cme DOT nist DOT gov (Ernie Kent)
Reply-To: coombs AT cme DOT nist DOT gov (Dave Coombs)
X-Phone: (301) 975-2865;  lab: 975-4080;  FAX: 990-9688;  secy: 975-3441
X-Mail: NIST, Robot Systems Div, Bldg 220 Rm B-124, Gaithersburg MD 20899 USA
Subject: Re: gcc.dvi 
Date: Wed, 17 Mar 93 16:34:47 -0500
From: David Coombs <coombs AT cme DOT nist DOT gov>
Content-Length: 1594
Status: RO
X-Lines: 52

I'm not sure where to start, so I'll try to give a fairly complete
transcript...

I started by guessing that the Texinfo info pages in the emacs info
reader might tell how to print the manuals.  I entered the info reader
in my emacs by typing

	C-h i

Then I chose the texinfo entry from the menu with

	mtexinfo

And I found an entry for printing the manuals.  There I got
instructions that amounted to 

	1. tex foo.tex
	2. texindex foo.??
	3. tex foo.tex
	4. dvips (or whatever you want to do with dvi files) foo

I decided to start with gcc.tex since it seemed like a top node sort
of place, but I didn't know it would include a lot of stuff.  [BTW, I
just noticed gcc didn't include cpp, so I just tex'd it too.]  So I
just went to the directory and said

	tex gcc.tex

It complained that it couldn't find a font, so I found the reference
in texinfo.tex and made it refer to a font that we have (in
/depot/tex/share/lib/fonts/tfm/... or somesuch; the tex man page tells
where).  You can find what I changed by grep'ing for my name to find
the comment I left.  So I fired up tex again,

	tex gcc.tex

and this time it only complained that it couldn't find invoke.texi,
and it was asking for an alternative, so I answered

	invoke.tex

and we were off to the races.  'Course I had to tell it about all the
other file names too.  That's why I recommended either changing the
file names or the @include commands so it will work automatically next
time.  

I tried to sort the indices, but we don't seem to have texindex
installed, so that's when I told you what I had.

Hope that helps.

dave


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019