diff options
author | /dev/humancontroller <devhc@example.com> | 2017-04-13 11:30:00 +0000 |
---|---|---|
committer | /dev/humancontroller <devhc@example.com> | 2017-04-15 12:11:01 +0200 |
commit | 60d92bbdcfc22c7248989ad7efb856989d299daa (patch) | |
tree | 74de9d4cb1f1a938705e13257ba136b9872b6600 /src/tools/lcc/doc/install.html | |
parent | 1a5afab2fcd1d43e5d43160ee601fa3bfa375a76 (diff) |
update the tools to the latest revision
URL: https://github.com/darklegion/tremulous
revision: c862a5340c8de44dcc7abaff170c20c04f9340e8, equivalently f45fbef604e05144057dec8d1dbfc5d4f5a2a822
Diffstat (limited to 'src/tools/lcc/doc/install.html')
-rw-r--r-- | src/tools/lcc/doc/install.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/tools/lcc/doc/install.html b/src/tools/lcc/doc/install.html index 3cc59a8..3410e8f 100644 --- a/src/tools/lcc/doc/install.html +++ b/src/tools/lcc/doc/install.html @@ -722,7 +722,7 @@ C:\dist\lcc\4.1>copy %BUILDDIR%\bprint.exe \bin <h2><a NAME="bugs">Reporting Bugs</a></h2> <p>lcc is a large, complex program. We find and repair errors routinely. If you think that -you've found a error, follow the steps below, which are adapted from the instructions in +you've found an error, follow the steps below, which are adapted from the instructions in Chapter 1 of <cite>A Retargetable C Compiler: Design and Implementation</cite>. <ol> @@ -751,7 +751,7 @@ Chapter 1 of <cite>A Retargetable C Compiler: Design and Implementation</cite>. HREF="ftp://ftp.cs.princeton.edu/pub/lcc"><code>pub/lcc</code></a>. A <a HREF="ftp://ftp.cs.princeton.edu/pub/lcc/README"><code>README</code></a> file there gives acquistion details, and the <a HREF="../LOG"><code>LOG</code></a> file reports what errors - were fixed and when they were fixed. If you report a error that's been fixed, you might + were fixed and when they were fixed. If you report an error that's been fixed, you might get a canned reply.</li> <li>Send your program by electronic mail to <code>lcc-bugs@cs.princeton.edu</code>. Please send only valid C programs; put all remarks in C comments so that we can process reports |