This is the mail archive of the
mailing list for the GCC project.
PATCH for Re: Should people need bison or is that a bug?
- To: Alexandre Oliva <aoliva at redhat dot com>
- Subject: PATCH for Re: Should people need bison or is that a bug?
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Date: Sat, 18 Nov 2000 14:09:02 +0100 (CET)
- cc: <Marco dot Franzen at thyron dot com>, <gcc at gcc dot gnu dot org>, <gcc-bugs at gcc dot gnu dot org>, <gcc-patches at gcc dot gnu dot org>
On 26 Oct 2000, Alexandre Oliva wrote:
>> According to <http://gcc.gnu.org/cvs.html#generated_files>, people
>> should not need bison.
> That's no longer true for CVS check-outs, but it's true for releases.
> Would you be kind enough to post a patch to update the web page and
> the update script? :-)
Well, I haven't seen such a patch until now, sooo I gave it a try.
RCS file: /cvs/gcc/wwwdocs/htdocs/cvs.html,v
retrieving revision 1.43
diff -u -3 -p -r1.43 cvs.html
--- cvs.html 2000/10/13 23:54:30 1.43
+++ cvs.html 2000/11/18 13:06:11
@@ -55,20 +55,16 @@ additional information on how to use CVS
<h3><a name="generated_files"></a>Generated files</h3>
-<p>The script <code>contrib/gcc_update</code> in the GCC CVS source
-tree will update the time stamps for the generated files within the source
-tree. If you have not made changes to the source for these generated
-files, it is safe to run <code>gcc_update</code>. See the comments
-in that script for instructions on running it.
-<p>The CVS source tree contains a number of files that are generated
+<p>Our CVS source tree contains a number of files that are generated
from other source files by build tools such as Bison, Autoconf, and
-Gperf. These generated files are included in the source tree so
-that GCC can be built without these build tools. The CVS checkout
-and update operations do not insure that the timestamps of generated
-files are later than those of the files they are generated from. The
-<code>gcc_update</code> script updates the timestamps for all the
+Gperf. Bison is now required when using CVS to access our sources,
+but all other generated files are included in the source tree so that
+GCC can be built without these build tools. The CVS checkout and
+update operations do not insure that the timestamps of generated files
+are later than those of the files they are generated from. The script
+<code>contrib/gcc_update</code> updates the timestamps for all these
+generated files. See the comments in that script for instructions on
<p>GCC's build system (in particular Make) uses file timestamps to
determine if a generated file needs to be updated by running a particular
@@ -78,7 +74,7 @@ changed, and require a particular build
file. If the appropriate build tool is installed on your system, then
this will not be a problem. If you do not intend to make changes to
the source, you can avoid installing these build tools by running
<p>There has been some discussion of removing these generated files
from GCC's CVS source tree (there is no discussion of removing them
@@ -86,13 +82,13 @@ from them from the released source tarba
building GCC from the CVS source tree would require installing
the above mentioned build tools. Installing these build tools is not
particularly difficult, but can be time consuming especially if you
-only occasionally install GCC on a particular system.
+only occasionally install GCC on a particular system.</p>
<p>The build tools that GCC uses are all available from the GNU
Project (see <a href="http://www.gnu.org">http://www.gnu.org</a>),
are often already available on many systems, and can often be found
already built for some systems. A partial list of these build tools
-is: Autoconf, Bison, Xgettext, Automake, and Gperf.
+is: Autoconf, Bison, Xgettext, Automake, and Gperf.</p>
<h3>CVS tags and checkouts</h3>