This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
other/567: "make dvi" fails
- To: gcc-gnats at gcc dot gnu dot org
- Subject: other/567: "make dvi" fails
- From: Joseph Myers <jsm28 at cam dot ac dot uk>
- Date: Sun, 24 Sep 2000 12:50:12 +0000
- Cc: jsm28 at cam dot ac dot uk
- Resent-Cc: gcc-prs at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org
- Resent-Reply-To: gcc-gnats@gcc.gnu.org, Joseph Myers <jsm28@cam.ac.uk>
>Number: 567
>Category: other
>Synopsis: "make dvi" fails
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Sep 24 05:56:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator: Joseph S. Myers
>Release: 2.96
>Organization:
none
>Environment:
System: Linux decomino 2.2.17 #1 Mon Sep 4 20:22:16 UTC 2000 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
>Description:
"make dvi" is broken.
I build outside the source directory, then, having built, do "make
dvi" in the builddir/gcc/ directory. In due course the build reaches
cd ch ; \
TEXINPUTS=:../../gcc-cvs/gcc:$TEXINPUTS tex chill.texi ; \
texindex chill.?? ; \
TEXINPUTS=:../../gcc-cvs/gcc:$TEXINPUTS tex chill.texi
This is TeX, Version 3.14159 (Web2C 7.2)
! I can't find file `chill.texi'.
<*> chill.texi
Please type another input file name:
Note that it is searching the wrong relative source directory here (in
TEXINPUTS); it should be ../../../gcc-cvs/gcc/ch (with the extra ../
and /ch).
On entering the full file name, the build continues and later fails
with
Output written on g77.dvi (350 pages, 1752740 bytes).
Transcript written on g77.log.
make: *** No rule to make target `java.dvi', needed by `lang.dvi'. Stop.
There don't seem to be any testing criteria for checking in
documentation patches, but I think both "make info" and "make dvi"
(and a look at the formatted output) should be there for any
documentation patch that goes beyond changing existing
subsections/nodes of the manual (preferably for any documentation
change at all). This of course requires "make dvi" to be working
first before it can be used to test documentation changes.
>How-To-Repeat:
See above.
>Fix:
Fix "make dvi" in whatever way is appropriate. Then consider adding
testing criteria for documentation changes. People running
autobuilders might wish to consider including "make dvi".
>Release-Note:
>Audit-Trail:
>Unformatted: