+2004-11-04 Joseph S. Myers <joseph@codesourcery.com>
+
+ * doc/gty.texi, doc/makefile.texi, doc/sourcebuild.texi: Don't
+ reference specific C parser files in examples.
+
2004-11-04 Richard Sandiford <rsandifo@redhat.com>
PR target/15342
The file will be called @file{gt-@var{path}.h} where @var{path} is the
pathname relative to the @file{gcc} directory with slashes replaced by
@verb{|-|}, so for example the header file to be included in
-@file{objc/objc-parse.c} is called @file{gt-objc-objc-parse.c}. The
+@file{cp/parser.c} is called @file{gt-cp-parser.c}. The
generated header file should be included after everything else in the
source file. Don't forget to mention this file as a dependency in the
@file{Makefile}!
@item srcextra
Generates files in the source directory that do not exist in CVS but
-should go into a release tarball. One example is @file{gcc/c-parse.c}
-which is generated from the CVS source file @file{gcc/c-parse.in}.
+should go into a release tarball. One example is @file{gcc/java/parse.c}
+which is generated from the CVS source file @file{gcc/java/parse.y}.
@item srcinfo
@itemx srcman
errors.
@item srcextra
Copies its dependencies into the source directory. This generally should
-be used for generated files such as @file{gcc/c-parse.c} which are not
+be used for generated files such as Bison output files which are not
present in CVS, but should be included in any release tarballs. This
target will be executed during a bootstrap if
@samp{--enable-generated-files-in-srcdir} was specified as a