Mail Archives: djgpp-workers/1998/06/26/18:43:59
This is a multi-part message in MIME format.
--------------3A0155EAF4D18A249D81DE3E
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Martin Str|mberg wrote:
>
> Some spelling and punctuation corrections to djgpp/gnu/gcc-2.81/readme.djg
> follows. As I'm not an English native speaker perhaps somebody has any
> comments?
I had a look, and came up with the following. This includes Martin's
patch, and so should be applied instead of it. (That patch wouldn't fit
exactly; I didn't investigate why.)
If my mailer uuencodes this, I will shoot it!
Thanks for the port!
--
Nate Eldredge
nate AT cartsys DOT com
--------------3A0155EAF4D18A249D81DE3E
Content-Type: text/plain; charset=us-ascii; name="readme.djgpp.diff"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="readme.djgpp.diff"
--- readme.djgpp.orig Fri Jun 26 15:05:34 1998
+++ readme.djgpp Fri Jun 26 15:33:36 1998
@@ -2,25 +2,24 @@
different zip-archives for the sources and the binaries.
The source archive gcc281s.zip contains all the sources to build
-the C, C++ and OBJC compiler. GNU FORTRAN compiler source archive is in
+the C, C++ and OBJC compilers. GNU FORTRAN compiler source is in
archive g770523s.zip and should be unzipped AFTER gcc281s.zip as
-it contains replacements from some files in gcc281s
-But the binary archives are split
-into four parts:
+it contains replacements for some files in gcc281s.zip.
+But the binary archives are split into four parts:
gcc281b.zip : The gcc.exe driver program and the C compiler.
- It contains also the documentation.
+ It also contains the documentation.
gpp281b.zip : The C++ compiler and libstdcxx.a (2.8.1.1) together
with needed header files
objc281b.zip : The OBJC compiler and libobjc.a and the needed
header files.
g770523b.zip : GNU Fortran compiler (version 0.5.23) and libg2c.a
- and g2f.h. Contains also replacement of gcc.exe but
+ and g2f.h. Also contains replacement of gcc.exe but
this file only provides compilation of Fortran sources
by gcc.exe but is NOT needed for g77.exe (this is
different from previous versions of g77)
-The archive gcc281b.zip is required also by gpp281b.zip, objc281b.zip
+The archive gcc281b.zip is also required by gpp281b.zip, objc281b.zip
and g770523b.zip
Please also consider that g77 is still in beta stage and I'm not going
@@ -30,25 +29,25 @@
============================
The DJGPP distribution of gcc 2.8.1 is now different from the one used
-by gcc 2.7.x. Now the directory structure is more similar to the
+by gcc 2.7.x. Now the directory structure is more similar to that of
unix systems and also all the DJGPP standard directories are hardcoded
already.
-To get no trouble, should remove at least you old gcc installation
+To get no trouble, you should remove at least your old gcc installation
completely, especially the compilers (cc1.exe, cc1plus.exe ...) and
libgcc.a, because they will not overwritten by the new distribution.
If you don't remove them, and you don't modify your djgpp.env file,
-gcc from gcc281b.zip will still uses these old binaries or the libgcc.a
-because they are in directories, which are searched before the hardcoded
+gcc from gcc281b.zip will still use these old binaries or the libgcc.a
+because they are in directories which are searched before the hardcoded
ones.
-I also recommend remove files 'specs' and 'djgpp.djl' from %DJDIR/lib.
+I also recommend removing the files 'specs' and 'djgpp.djl' from %DJDIR/lib.
Archive gcc281b.zip contains replacement for these files which will
go to a different directory %DJDIR/lib/gcc-lib/djgpp/2.81.
-If You have changed any of these 2 files You can consider to transfer
-these changes to new files. It is possible to avoid removing these files
-but don't do this unless You know what You are doing.
+If you have changed either of these 2 files you might consider transferring
+these changes to the new files. It is possible to avoid removing these files
+but don't do this unless you know what you are doing.
Additionally you can safely remove the [gcc] and [cpp] section from your
djgpp.env file, since the path-settings there are not longer needed, because
@@ -57,7 +56,7 @@
have some of your own directories searched by default, you should leave
only those directories there and remove the standard DJGPP directories.
-Modifying the djgpp.env is not really neccessary, but recommended by me.
+Modifying the djgpp.env is not really necessary, but I recommend it.
I'm including an example of modified DJGPP.ENV in directory gnu/gcc-2.81
I have tested it with gcc-2.8.1
@@ -81,7 +80,7 @@
Install them like any other DJGPP binary archive:
-- change to your DJGPP base directory (normally c:/djgpp) and unzip
+- change to your DJGPP base directory (often c:/djgpp) and unzip
there the archive
unzip gcc281b.zip
@@ -93,9 +92,9 @@
Installing under Windows 95
===========================
-If you want to install and use gcc under Windows 95 you should remember
-that this OS can handle long and case sensetive filenames. Here ar three
-cases:
+If you want to install and use gcc under Windows 95, you should remember
+that this OS can handle long and case sensitive filenames. Here are
+three cases:
1. Only long filenames
----------------------
@@ -106,25 +105,25 @@
2. Only short filenames
-----------------------
-Unzip the binaries with an unzip program, which doesn't know about long
-filenames, or if your unzipper knows about them, please follow at first
-the steps descripbed in the DJGPP FAQ 2.01 in section
+Unzip the binaries with an unzip program which doesn't know about long
+filenames, or if your unzipper knows about them, please follow first
+the steps described in the DJGPP FAQ 2.01 in the section
about setting the NameNumericTail to 0 __BEFORE__!!! unzipping the archives.
3. Long and short filenames at the same time
--------------------------------------------
-Use an unzip program which can restore the long filenames and do the
-same like under 2. when the unzipper knows about long filenames.
+Use an unzip program which can restore the long filenames and follow
+the instructions under 2. when the unzipper knows about long filenames.
DJGPP specific hints for C++
============================
-Since there are still some long filename problems, which could not be solved
-in an easy way, there are some tricks to get all the functionallity in C++.
-Especially some headers are renamed to get no confilcts with either each other
-or with existing heeader files from libc.
+Since there are still some long filename problems which could not be solved
+in an easy way, there are some tricks to get all the functionality in C++.
+Especially, some headers are renamed to avoid conflicts with either each other
+or with existing header files from libc.
I list here all the relevant header files and how they are named for DJGPP
@@ -136,13 +135,13 @@
So there are now two ways to include these headers. Either use the DJGPP
specific name or use a new feature of the preprocessor cpp. It accepts now
a new commandline switch "-remap" which tells cpp to look in a directory
-for a file named "header.gcc" and the it takes that file as a translation
+for a file named "header.gcc". It takes that file as a translation
table if a requested file was not found in the directory.
-The DJGPP distribution of g++ and libg++ come already with these translation
+The DJGPP distribution of g++ and libg++ already come with these translation
files, but they are currently not used. To use them, you have to modify your
specs file to add the "-remap" switch to the call for cpp, since this switch
-cannot passed to cpp from the gcc comanndline. Here is now a possible line
+cannot passed to cpp from the gcc comanndline. Here is a possible line
from the spec file in your lib/ directory:
*cpp:
@@ -162,9 +161,9 @@
- gcc library search path contains $DJDIR/lib
- $DJDIR/lib contains old versions of djgpp.djl and(or) specs from
djdev201.zip
-are true, then old files will be used errorously. If You have editted
-DJGPP.ENV as recommended above (or used version supplied with archive
-gcc281b.zip) correct version will be used. Anyway I recommend to
+are true, then old files will be used erroneously. If you have edited
+DJGPP.ENV as recommended above (or used the version supplied with archive
+gcc281b.zip), the correct version will be used. Anyway, I recommend to
remove old versions of these files from $DJDIR/lib.
Possible problems with exceptions handling under gcc-2.81
@@ -186,8 +185,8 @@
Requirememts
------------
-To build gcc you need many GNU utilities installed. This includes at very
-first bash and a symlink sh to it.
+To build gcc you need many GNU utilities installed. This includes at the
+very least bash and a symlink sh to it.
********
To get it, change to the DJGPP bin directory and type there
@@ -208,7 +207,7 @@
- txi390b.zip
And you need about 40 MB free disk space as minimum, when you build without
-debugging information (with debug info I would guess about 50 MB)
+debugging information (with debug info I would guess about 50 MB).
Extracting the sources
----------------------
@@ -222,12 +221,12 @@
At first you should unzip the archive gcc281s.zip. The sources are _NOT_
the complete sources like the original gcc 2.8.1 distribution. I have
removed many files to save disk space which are not needed for the DJGPP
-port. I removed also many of the older Changelog-files.
+port. I also removed many of the older Changelog-files.
The sources are already configured, but if you want to reconfigure them,
please use _ONLY_ the script file 'djconfig.sh' (written by Robert
Hoehne) instead of running the configure script, since it does some
-tricks before running configure. (read the comments inside this file!!).
+tricks before running configure. (Read the comments inside this file!!).
To run it you must have bash installed and a symlink sh.exe to bash.exe.
I configured sources to be compiled in directory build.djg.
@@ -238,8 +237,8 @@
Robert Hoehne wrote also another script 'djmake.sh' to be used instead
-of simply make. Like above: Please use _ONLY_ this script instead of
-running a simply make (except of course you know what you do).
+of simply make. As above: Please use _ONLY_ this script instead of
+running a simple make (unless of course you know what you're doing).
Now you run make by typing
@@ -249,16 +248,16 @@
make [any-additional-parameter]
-I did only small changes to these scripts.
+I made only small changes to these scripts.
-Compiling in an other directory
+Compiling in another directory
-------------------------------
I configured gcc to be compiled in directory build.djg. To change this
-directory You should move it contents to desired location and modify
-both scripts (djconfig.sh and djmake.sh) to set exact path to sources.
-After that You can use these scripts as described above.
+directory you should move its contents to the desired location and modify
+both scripts (djconfig.sh and djmake.sh) to set the exact path to sources.
+After that, you can use these scripts as described above.
Installing the newly built binaries
@@ -269,8 +268,8 @@
sh djmake.sh prefix=$DJDIR install
This is needed, because by default the Makefile has a prefix which
-will not allow to install the files correct because Robert Hoehne made
-there a trick when configuring gcc to have the $DJGPP variable hardcoded in
+will not allow the files to be installed correctly because Robert Hoehne used
+a trick when configuring gcc to have the $DJGPP variable hardcoded in
the binaries instead of the expanded value of this variable.
Reporting bugs
@@ -278,12 +277,12 @@
If you found a bug in gcc, please report it to the gcc bug adresses and _NOT_
(or at least not only) in the DJGPP news group. But if you think you found
-a bug in the DJGPP related things, the please report in comp.os.msdos.djgpp
+a bug in the DJGPP related things, then please report it in comp.os.msdos.djgpp
(the news group) or mail it to djgpp AT delorie DOT com, which is the gateway to
the news group.
Please email me directly only in rare cases, if you think it is only of
-interest for me, since I see the reports in comp.os.msdos.djgpp also.
+interest to me, since I see the reports in comp.os.msdos.djgpp also.
Credits
@@ -291,7 +290,7 @@
Thanks to Robert H?hne <robert DOT hoehne AT gmx DOT net> for his DJGPP port of
gcc-2.8.0 which was used as a base of this port and his help (including
-exception support)
+exception support).
Have fun with gcc,
@@ -299,8 +298,8 @@
Andris Pavenis <pavenis AT lanet DOT lv>
----------------------------------------------------------------------
-patch to autoheader. Neaded ONLY if you need to run autoheader under
-Windows 95. Normally NOT NEEDED to build gcc unless You modify Configure.in
+patch to autoheader. Nedeed ONLY if you need to run autoheader under
+Windows 95. Normally NOT NEEDED to build gcc unless you modify Configure.in
----------------- patch to autoheader ------------------------
*** autoheader~ Wed May 14 17:33:34 1997
--- autoheader Tue Mar 24 15:03:18 1998
--------------3A0155EAF4D18A249D81DE3E--
- Raw text -