-Building egcs-1.00
+Building egcs-1.0
-Now that egcs is configured, you are ready to build the compiler and runtime
-libraries.
+Now that egcs is configured, you are ready to build the compiler and
+runtime libraries.
-We highly recommend that egcs be built using gnu-make; other versions make
-work, then again they might not. To be safe build with gnu-make.
+We highly recommend that egcs be built using gnu-make; other
+versions make work, then again they might not. To be safe build with gnu-make.
-Building a native compiler
+Building a native compiler
+For a native build issue the command "make bootstrap". This will build
+the entire egcs compiler system, which includes the following steps:
-For a native build issue the command "make bootstrap". This will build the
-entire egcs compiler system, which includes the following steps:
- * Build host tools necessary to build the compiler such as texinfo, bison,
- gperf.
+ Build host tools necessary to build the compiler such as texinfo, bison,
+ gperf.
- * Build target tools for use by the compiler such as gas, gld, and binutils.
+ Build target tools for use by the compiler such as gas, gld, and binutils.
- * Perform a 3-stage bootstrap of the compiler.
+ Perform a 3-stage bootstrap of the compiler.
- * Perform a comparison test of the stage2 and stage3 compilers.
+ Perform a comparison test of the stage2 and stage3 compilers.
- * Build runtime libraries using the stage3 compiler from the previous step.
+ Build runtime libraries using the stage3 compiler from the previous step.
If you are short on disk space you might consider "make bootstrap-lean"
-instead. This is identical to "make bootstrap" except that object files from the
-stage1 and stage2 of the 3-stage bootstrap of the compiler are deleted as soon
-as they are no longer needed. Building a cross compiler
+instead. This is identical to "make bootstrap" except that object files
+from the stage1 and stage2 of the 3-stage bootstrap of the compiler are
+deleted as soon as they are no longer needed.
-We recommend reading the crossgcc FAQ for information about building cross
-compilers. (ftp.cygnus.com:pub/crossgcc)
+Building a cross compiler
+
+We recommend reading the crossgcc FAQ for information about building
+cross compilers.
+"ftp://ftp.cygnus.com/pub/embedded/crossgcc/FAQ-0.8.1"
For a cross build, issue the command "make cross", which performs the
-following steps:
+following steps:
+
+ Build host tools necessary to build the compiler such as texinfo, bison,
+ gperf.
+
+ Build target tools for use by the compiler such as gas, gld, and binutils.
- * Build host tools necessary to build the compiler such as texinfo, bison,
- gperf.
+ Build the compiler (single stage only).
- * Build target tools for use by the compiler such as gas, gld, and binutils.
+ Build runtime libraries using the compiler from the previous step.
- * Build the compiler (single stage only).
- * Build runtime libraries using the compiler from the previous step.
+Note that if an error occurs in any step the make process will exit.
-Note that if an error occurs in any step the make process will exit.
+Last modified on December 2, 1997.
-Configuring egcs-1.00
+Configuring egcs-1.0
-Like most GNU software, egcs must be configured before it can be built. This
-document attempts to describe the recommended configuration procedure for
-both native and cross targets.
+Like most GNU software, egcs must be configured before it can be built.
+This document attempts to describe the recommended configuration procedure
+for both native and cross targets.
-We use srcdir to refer to the toplevel source directory for egcs; we use objdir
-to refer to the toplevel build/object directory for egcs.
+We use srcdir to refer to the toplevel source directory for
+egcs; we use objdir to refer to the toplevel build/object
+directory for egcs.
-First, we highly recommend that egcs be built into a separate directory than the
-sources. This is how we generally build egcs; building where srcdir == objdir
-should still work, but doesn't get extensive testing.
+First, we highly recommend that egcs be built into a separate
+directory than the sources. This is how we generally build egcs; building
+where srcdir == objdir should still work, but doesn't get
+extensive testing.
-Second, when configuring a native system, either "cc" must be in your path or
-you must set CC in your environment before running configure. Otherwise the
-configuration scripts may fail.
+Second, when configuring a native system, either "cc" must be in your
+path or you must set CC in your environment before running configure.
+Otherwise the configuration scripts may fail.
-To configure egcs:
+To configure egcs:
- % mkdir objdir
- % cd objdir
- % srcdir/configure [target] [options]
+ % mkdir objdir
+ % cd objdir
+ % srcdir/configure [target] [options]
-target specification
- egcs has code to correctly determine the correct value for target for
- nearly all native systems. Therefore, we highly recommend you not
- provide a configure target when configuring a native compiler.
- target must be specified when configuring a cross compiler; examples of
- valid targets would be i960-rtems, m68k-coff, sh-elf, etc.
+target specification
-options specification
+ egcs has code to correctly determine the correct value for
+ target for nearly all native systems. Therefore, we highly
+ recommend you not provide a configure target when configuring a
+ native compiler.
-Use options to override several configure time options for egcs. A partial list
-of supported options:
+ target must be specified when configuring a cross compiler;
+ examples of valid targets would be i960-rtems, m68k-coff, sh-elf, etc.
- * --prefix=dirname -- Specify the toplevel installation directory;
- /usr/local is the default prefix. This is the recommended way to install
- the tools into a directory other than the default.
- These additional options control where certain parts of the distribution
- are installed. Normally you should not need to use these options.
- --with-local-prefix=dirname -- Specify the installation
- directory for local include files. The default is /usr/local.
- --with-gxx-include-dir=dirname -- Specify the installation
- directory for g++ header files. The default is
- /usr/local/include/g++.
- * --enable-shared -- Build shared libraries if supported
- --disable-shared is the default.
+options specification
- * --enable-haifa -- Enable the new Haifa instruction scheduler in the
- compiler; the new scheduler can significantly improve code on some
- targets. --disable-haifa is currently the default on all platforms
- except the HPPA.
+Use options to override several configure time options for
+egcs. A partial list of supported options:
- * --with-gnu-as -- Specify that the compiler should assume the GNU
- assembler (aka gas) is available.
- * --with-gnu-ld -- Specify that the compiler should assume the GNU
- linker (aka gld) is available.
+ --prefix=dirname -- Specify the toplevel installation
+ directory. This is the recommended way to install the tools into a directory
+ other than the default. The toplevel installation directory defaults to
+ /usr/local.
- * --with-stabs -- Specify that stabs debugging information should be
- used instead of whatever format the host normally uses. Normally GCC
- uses the same debug format as the host system.
+ These additional options control where certain parts of the distribution
+ are installed. Normally you should not need to use these options.
+
+ --with-local-prefix=dirname -- Specify the installation
+ directory for local include files. The default is /usr/local.
- * --enable-multilib -- Specify that multiple libraries should be built
- to support different target variants, calling conventions, etc. This is the
- default.
+ --with-gxx-include-dir=dirname -- Specify the installation
+ directory for g++ header files. The default is /usr/local/include/g++.
+
- * --enable-threads -- Specify that the target supports threads.
- * --enable-threads=lib -- Specify that lib is the thread support
- library.
+ --enable-shared -- Build shared versions of the C++ runtime
+ libraries if supported --disable-shared is the default.
- * --with-cpu=cpu -- Specify which cpu variant the compiler should
- generate code for by default. This is currently only supported on the
- RS6000/PowerPC ports.
+ --enable-haifa -- Enable the new Haifa instruction scheduler in the
+ compiler; the new scheduler can significantly improve code on some targets.
+ --disable-haifa is currently the default on all platforms except the HPPA.
-Some options which only apply to building cross compilers:
+ --with-gnu-as -- Specify that the compiler should assume the GNU
+ assembler (aka gas) is available.
- * --with-headers=dir -- Specifies a directory which has target include
- files.
+ --with-gnu-ld -- Specify that the compiler should assume the GNU
+ linker (aka gld) is available.
- * --with-libs=dirs -- Specifies a list of directories which contain the
- target runtime libraries.
+ --with-stabs -- Specify that stabs debugging information should be used
+ instead of whatever format the host normally uses. Normally GCC uses the
+ same debug format as the host system.
- * --with-newlib -- Specifies that "newlib" is being used as the target C
- library. This causes __eprintf to be omitted from libgcc.a on the
- assumption that it will be provided by newlib.
+ --enable-multilib -- Specify that multiple target libraries
+ should be built to support different target variants, calling conventions,
+ etc. This is the default.
+ --enable-threads -- Specify that the target supports threads.
+ This only effects the Objective-C compiler and runtime library.
+
+ --enable-threads=lib -- Specify that lib is the
+ thread support library. This only effects the Objective-C compiler and
+ runtime library.
+
+ --with-cpu=cpu -- Specify which cpu variant the compiler should
+ generate code for by default. This is currently only supported on the
+ RS6000/PowerPC ports.
+
+
+Some options which only apply to building cross compilers:
+
+ --with-headers=dir -- Specifies a directory which has target
+ include files.
+ --with-libs=dirs -- Specifies a list of directories which contain
+ the target runtime libraries.
+ --with-newlib -- Specifies that "newlib" is being used as the target
+ C library. This causes __eprintf to be omitted from libgcc.a on the
+ assumption that it will be provided by newlib.
+
+
Note that each --enable option has a corresponding --disable option and
-that each --with option has a corresponding --without option.
+that each --with option has a corresponding --without option.
+
+Last modified on December 2, 1997.
-Final install egcs-1.00
+Final install egcs-1.0
Now that egcs has been built and tested, you can install it with
`cd objdir; make install' for a native compiler or
-`cd objdir; make install LANGUAGES="c gcov c++"' for a cross compiler (note
-installing cross compilers will be easier in the next release!).
+`cd objdir; make install LANGUAGES="c c++"' for a cross compiler
+(note installing cross compilers will be easier in the next release!).
-That step completes the installation of egcs; user level binaries can be found
-in prefix/bin where prefix is the value you specified with the --prefix to
-configure (or /usr/local by default).
-If you don't mind, please send egcs@cygnus.com a short mail message indicating
-that you successfully built and installed egcs. Include the output from running
-srcdir/config.guess.
+That step completes the installation of egcs; user level binaries can
+be found in prefix/bin where prefix is the value you specified
+with the --prefix to configure (or /usr/local by default).
-If you find a bug in egcs, please report it to egcs-bugs@cygnus.com.
+If you don't mind, please send egcs@cygnus.com a short mail message
+indicating that you successfully built and installed egcs. Include
+the output from running srcdir/config.guess.
+If you find a bug in egcs, please report it to egcs-bugs@cygnus.com
+Last modified on December 2, 1997.
- Installing egcs-1.00
+Installing egcs-1.0
-This document describes the generic installation procedure for egcs as well as
-detailing some target specific installation instructions for egcs.
+This document describes the generic installation procedure for egcs as
+well as detailing some target specific installation instructions for egcs.
egcs includes several components that previously were separate distributions
-with their own installation instructions. This document supercedes all package
-specific installation instructions. We provide the component specific
+with their own installation instructions. This document supercedes all
+package specific installation instructions. We provide the component specific
installation information in the source distribution for historical reference
-purposes only.
+purposes only.
-We recommend you read the entire generic installation instructions as well as
-any target specific installation instructions before you proceed to configure,
-build, test and install egcs.
+We recommend you read the entire generic installation instructions as
+well as any target specific installation instructions before you proceed
+to configure, build, test and install egcs.
-If something goes wrong in the configure, build, test or install procedures,
-first double check that you followed the generic and target specific
-installation instructions carefully. Then check the FAQ to see if your problem
-is covered before you file a bug report.
+If something goes wrong in the configure, build, test or install
+procedures, first double check that you followed the generic and target
+specific installation instructions carefully. Then check the EGCS FAQ
+(FAQ) to see if your problem is covered before you file a bug report.
-The installation procedure is broken into four steps.
+The installation procedure is broken into four steps.
- configure CONFIGURE
- build BUILD
- test (optional) TEST
- install FINALINSTALL
-Before starting the build/install procedure please browse the host/target specific installation notes (SPECIFIC).
+ Configure see CONFIGURE
+ Build see BUILD
+ Test see TEST
+ Final Install see FINALINSTALL
+
+
+Before starting the build/install procedure please browse the
+host/target specific installation notes (SPECIFIC).
+
+Last modified on December 2, 1997.
+
-Host/Target specific installation notes for
- egcs-1.00
+Host/Target specific installation notes for egcs-1.0
alpha*-*-*
-No specific installation needs/instructions.
+No specific installation needs/instructions.
-i?86-*-linux-*
-You will need binutils-2.8.1.0.15 or newer for exception handling to work.
+
+i?86-*-linux*
+You will need binutils-2.8.1.0.15 or newer for exception handling to work.
i?86-*-sco3.2v5*
-The SCO assembler is currently required. The GNU assembler is not up to the
-task of switching between ELF and COFF at runtime.
-Unlike various prereleases of GCC, that used '-belf' and defaulted to COFF,
-you must now use the '-melf' and '-mcoff' flags to toggle between the two
-object file formats. ELF is now the default.
+The SCO assembler is currently required. The GNU assembler is not up
+to the task of switching between ELF and COFF at runtime.
+
+Unlike various prereleases of GCC, that used '-belf' and defaulted to
+COFF, you must now use the '-melf' and '-mcoff' flags to toggle between
+the two object file formats. ELF is now the default.
+
Look in gcc/config/i386/sco5.h (search for "messy") for additional
-OpenServer-specific flags.
+OpenServer-specific flags.
+
+
hppa*-hp-hpux*
-We highly recommend using gas/binutils-2.8 on all hppa platforms; you may
-encounter a variety of problems when using the HP assembler. XXX How to
-make sure gcc finds/uses gas.
+We highly recommend using gas/binutils-2.8 on all hppa platforms; you
+may encounter a variety of problems when using the HP assembler.
hppa*-hp-hpux9
-The HP assembler has major problems on this platform. We've tried to work
-around the worst of the problems. However, those workarounds may be causing
+The HP assembler has major problems on this platform. We've tried to work
+around the worst of the problems. However, those workarounds may be causing
linker crashes in some circumstances; the workarounds also probably prevent
-shared libraries from working. Use the GNU assembler to avoid these
-problems.
+shared libraries from working. Use the GNU assembler to avoid these problems.
-The configuration scripts for egcs will also trigger a bug in the hpux9 shell.
-To avoid this problem set CONFIG_SHELL to /bin/ksh and SHELL to /bin/ksh in
-your environment.
+The configuration scripts for egcs will also trigger a bug in the hpux9
+shell. To avoid this problem set CONFIG_SHELL to /bin/ksh and SHELL to
+/bin/ksh in your environment.
hppa*-hp-hpux10
-For hpux10.20, we highly recommend you pick up the latest sed patch from
-HP. HP has two sites which provide patches free of charge.
-US, Canada, Asia-Pacific, and Latin-America
-Europe
+For hpux10.20, we highly recommend you pick up the latest sed
+patch from HP. HP has two sites which provide patches free of charge.
-Retrieve patch PHCO_12862.
+http://us-support.external.hp.com for US, Canada, Asia-Pacific, and
+Latin-America
+http://europe-support.external.hp.com for Europe
+Retrieve patch PHCO_12862.
The HP assembler on these systems is much better than the hpux9 assembler,
-but still has some problems. Most notably the assembler inserts timestamps
+but still has some problems. Most notably the assembler inserts timestamps
into each object file it creates, causing the 3-stage comparison test to fail
-during a "make bootstrap". You should be able to continue by saying "make
-all" after getting the failure from "make bootstrap".
+during a "make bootstrap". You should be able to continue by saying "make all"
+after getting the failure from "make bootstrap".
m68k-*-nextstep*
-You absolutely must use GNU sed and GNU make on this platform. If you try
-to build the integrated C++ & C++ runtime libraries on this system you will
-run into trouble with include files. The way to get around this is to use the
-following sequence. Note you must have write permission to prefix for this
-sequence to work.
+You absolutely must use GNU sed and GNU make on this platform.
+If you try to build the integrated C++ & C++ runtime libraries on this system
+you will run into trouble with include files. The way to get around this is
+to use the following sequence. Note you must have write permission to
+prefix for this sequence to work.
cd objdir
make all-texinfo all-bison all-byacc all-binutils all-gas all-ld
m68k-sun-sunos4.1.1
It is reported that you may need the GNU assembler on this platform.
-
mips*-sgi-irix4
mips*-sgi-irix5
You must use GAS on these platforms, the native assembler can not handle the
-code for exception handling support on this platform. These systems don't have
-ranlib, which various components in egcs need; you should be able to avoid this
-problem by installing GNU binutils, which includes a functional ranlib for this
-system.
+code for exception handling support on this platform.
+
+These systems don't have ranlib, which various components in egcs need; you
+should be able to avoid this problem by installing GNU binutils, which includes
+a functional ranlib for this system.
You may get the following warning on irix4 platforms, it can be safely
-ignored.
+ignored.
warning: foo.o does not have gp tables for all its sections.
-
mips*-sgi-irix6
-You must not use GAS on irix6 platforms; doing so will only cause problems.
+You must not use GAS on irix6 platforms; doing so will only cause problems.
-These systems don't have ranlib, which various components in egcs need; you should be able to avoid
-this problem by making a dummy script called ranlib which just exits with zero status and placing it in
-your path.
+These systems don't have ranlib, which various components in egcs need; you
+should be able to avoid this problem by making a dummy script called ranlib
+which just exits with zero status and placing it in your path.
rs6000-ibm-aix*
powerpc-ibm-aix*
At least one person as reported problems with older versions of gnu-make on
-this platform. make-3.76 is reported to work correctly.
+this platform. make-3.76 is reported to work correctly.
powerpc-*-linux-gnu*
-You will need binutils-2.8.1.0.17 for a working egcs. It is strongly
-recommended to recompile binutils with egcs if you initially built it with
-gcc-2.7.2.*.
+You will need binutils-2.8.1.0.17 from ftp://ftp.yggdrasil.com/private/hjl for
+a working egcs. It is strongly recommended to recompile binutils with egcs
+if you initially built it with gcc-2.7.2.*.
+
+exception handling
+XXX Linux stuff
+Last modified on December 2, 1997.
-Testing egcs-1.00
+Testing egcs-1.0
-Before you install egcs, you might wish to run the egcs testsuite; this step is
-optional and may require you to download additional software.
+Before you install egcs, you might wish to run the egcs testsuite; this
+step is optional and may require you to download additional software.
First, you must have downloaded the egcs testsuites; the full distribution
-contains testsuites. If you downloaded the "core" compiler plus any front ends,
-then you do not have the testsuites. You can download the testsuites from the
-same site where you downloaded the core distribution and language front ends.
+contains testsuites. If you downloaded the "core" compiler plus any front
+ends, then you do not have the testsuites. You can download the testsuites
+from the same site where you downloaded the core distribution and language
+front ends.
Second, you must have a new version of dejagnu on your system; dejagnu-1.3
-will not work. We have made a dejagnu snapshot available in
-ftp.cygnus.com:/pub/egcs/infrastructure until a new version of dejagnu can be
-released.
+will not work. We have made a dejagnu snapshot
+ftp://ftp.cygnus.com/pub/egcs/infrastructure/dejagnu-971028.tar.gz
+dejagnu snapshot available in ftp.cygnus.com:/pub/egcs/infrastructure until
+a new version of dejagnu can be released.
Assuming you've got the testsuites unpacked and have installed an appropriate
-dejagnu, you can run the testsuite with "cd objdir; make -k check". This may
-take a long time. Go get some lunch.
+dejagnu, you can run the testsuite with "cd objdir; make -k check".
+This may take a long time. Go get some lunch.
-The testing process will try to test as many components in the egcs distrubution
-as possible, including the C, C++ and Fortran compiler as well as the C++
-runtime libraries.
+The testing process will try to test as many components in the egcs
+distrubution as possible, including the C, C++ and Fortran compiler as
+well as the C++ runtime libraries.
+ How to interpret test results XXX.
+
+Last modified on December 2, 1997.
<html>
<head>
-<title>Building egcs-1.00 </title>
+<title>Building egcs-1.0 </title>
</head>
<body bgcolor="white">
-<h1 align="center">Building egcs-1.00</h1>
+<h1 align="center">Building egcs-1.0</h1>
<p>Now that egcs is configured, you are ready to build the compiler and
runtime libraries.
<p>We <b>highly</b> recommend that egcs be built using gnu-make; other
versions make work, then again they might not. To be safe build with gnu-make.
-<p>
-<b>Building a native compiler</b>
+<p><b>Building a native compiler</b>
<p>For a native build issue the command "make bootstrap". This will build
the entire egcs compiler system, which includes the following steps:
from the stage1 and stage2 of the 3-stage bootstrap of the compiler are
deleted as soon as they are no longer needed.
-<b>Building a cross compiler</b>
+<p><b>Building a cross compiler</b>
<p> We recommend reading the
<a href="ftp://ftp.cygnus.com/pub/embedded/crossgcc/FAQ-0.8.1">
<p>
<hr>
-<i>Last modified on December 1, 1997.</i>
+<i>Last modified on December 2, 1997.</i>
</body>
</html>
<html>
<head>
-<title>Configuring egcs-1.00 </title>
+<title>Configuring egcs-1.0 </title>
</head>
<body bgcolor="white">
-<h1 align="center">Configuring egcs-1.00</h1>
+<h1 align="center">Configuring egcs-1.0</h1>
<p>Like most GNU software, egcs must be configured before it can be built.
This document attempts to describe the recommended configuration procedure
egcs. A partial list of supported <tt>options</tt>:
<ul>
- <li> <tt>--prefix=</tt><i>dirname</i> -- Specify the toplevel installation directory;
- /usr/local is the default prefix. This is the recommended way to install
- the tools into a directory other than the default.
+ <li> <tt>--prefix=</tt><i>dirname</i> -- Specify the toplevel installation
+ directory. This is the recommended way to install the tools into a directory
+ other than the default. The toplevel installation directory defaults to
+ /usr/local.
<br>These additional options control where certain parts of the distribution
are installed. Normally you should not need to use these options.
directory for g++ header files. The default is /usr/local/include/g++.
</ul>
- <li> <tt>--enable-shared</tt> -- Build shared libraries if supported
- <tt>--disable-shared</tt> is the default.
+ <li> <tt>--enable-shared</tt> -- Build shared versions of the C++ runtime
+ libraries if supported <tt>--disable-shared</tt> is the default.
<li> <tt>--enable-haifa</tt> -- Enable the new Haifa instruction scheduler in the
compiler; the new scheduler can significantly improve code on some targets.
instead of whatever format the host normally uses. Normally GCC uses the
same debug format as the host system.
- <li> <tt>--enable-multilib</tt> -- Specify that multiple libraries should be built
- to support different target variants, calling conventions, etc. This
- is the default.
+ <li> <tt>--enable-multilib</tt> -- Specify that multiple target libraries
+ should be built to support different target variants, calling conventions,
+ etc. This is the default.
- <li> <tt>--enable-threads</tt> -- Specify that the target supports threads.
+ <li> <tt>--enable-threads</tt> -- Specify that the target supports threads.
+ This only effects the Objective-C compiler and runtime library.
- <li> <tt>--enable-threads=</tt><i>lib</i> -- Specify that <i>lib</i> is the thread
- support library.
+ <li> <tt>--enable-threads=</tt><i>lib</i> -- Specify that <i>lib</i> is the
+ thread support library. This only effects the Objective-C compiler and
+ runtime library.
<li> <tt>--with-cpu=</tt><i>cpu</i> -- Specify which cpu variant the compiler should
generate code for by default. This is currently only supported on the
<p>
<hr>
-<i>Last modified on December 1, 1997.</i>
+<i>Last modified on December 2, 1997.</i>
</body>
</html>
<html>
<head>
-<title>Final install egcs-1.00 </title>
+<title>Final install egcs-1.0 </title>
</head>
<body bgcolor="white">
-<h1 align="center">Final install egcs-1.00</h1>
+<h1 align="center">Final install egcs-1.0</h1>
<p>Now that egcs has been built and tested, you can install it with
`cd <i>objdir</i>; make install' for a native compiler or
<p>
<hr>
-<i>Last modified on December 1, 1997.</i>
+<i>Last modified on December 2, 1997.</i>
</body>
</html>
<html>
<head>
-<title>Installing egcs-1.00 </title>
+<title>Installing egcs-1.0 </title>
</head>
<body bgcolor="white">
-<h1 align="center">Installing egcs-1.00</h1>
+<h1 align="center">Installing egcs-1.0</h1>
<p>This document describes the generic installation procedure for egcs as
well as detailing some target specific installation instructions for egcs.
</body>
</html>
<hr>
-<i>Last modified on December 1, 1997.</i>
+<i>Last modified on December 2, 1997.</i>
<html>
<head>
-<title>Host/Target specific installation notes for egcs-1.00 </title>
+<title>Host/Target specific installation notes for egcs-1.0 </title>
</head>
<body bgcolor="white">
-<h1 align="center">Host/Target specific installation notes for egcs-1.00</h1>
+<h1 align="center">Host/Target specific installation notes for egcs-1.0</h1>
<p><b>alpha*-*-*</b><br>
No specific installation needs/instructions.
<p>
exception handling
<p>XXX Linux stuff
--k encaps stuff
<hr>
-<i>Last modified on December 1, 1997.</i>
+<i>Last modified on December 2, 1997.</i>
</body>
</html>
<html>
<head>
-<title>Testing egcs-1.00 </title>
+<title>Testing egcs-1.0 </title>
</head>
<body bgcolor="white">
-<h1 align="center">Testing egcs-1.00</h1>
+<h1 align="center">Testing egcs-1.0</h1>
<p>Before you install egcs, you might wish to run the egcs testsuite; this
step is optional and may require you to download additional software.
<p> How to interpret test results XXX.
<hr>
-<i>Last modified on December 1, 1997.</i>
+<i>Last modified on December 2, 1997.</i>
</body>
</html>
-This directory contains the version 2.7.2 release of the GNU C
+This directory contains the egcs version 1.0 release of the GNU C
compiler. It includes all of the support for compiling C++ and
Objective C, including a run-time library for Objective C.
gcc C front end, and other non-Fortran files, and gcc/f/, which
contains all of the Fortran files.
+* Note, if this is an egcs release, all the installation information
+ which follows is not needed. It is provided for historical reference
+ only.
+
* To build GNU Fortran, you must have a source distribution of gcc
version 2.7.2.2. Do not attempt to use any other version
of gcc, because this version of g77 is designed to work only with
.if n .sp
.if t .sp 0.4
..
-.Id $Id: gcc.1,v 1.4 1993/10/13 23:19:12 pesch Exp $
+.Id $Id: gcc.1,v 1.1.1.1 1997/08/11 15:57:07 law Exp $
.TH GCC 1 "\*(Dt" "GNU Tools" "GNU Tools"
.SH NAME
-gcc, g++ \- GNU project C and C++ Compiler (v2.7)
+gcc, g++ \- GNU project C and C++ Compiler (egcs-1.0)
.SH SYNOPSIS
.B gcc
.RI "[ " option " | " filename " ].\|.\|."
@sp 1
@c The version number appears twice more in this file.
-@center for version 2.7.2
+@center for egcs-1.0
@page
@vskip 0pt plus 1filll
Copyright @copyright{} 1988, 89, 92, 93, 94, 95, 96 Free Software Foundation, Inc.
@sp 2
-For GCC Version 2.7.2@*
+For EGCS Version 1.0@*
@sp 1
Published by the Free Software Foundation @*
59 Temple Place - Suite 330@*
@ifset USING
This manual documents how to run, install and port the GNU
compiler, as well as its new features and incompatibilities, and how to
-report bugs. It corresponds to GNU CC version 2.7.2.
+report bugs. It corresponds to EGCS version 1.0.
@end ifset
@end ifset
@ifclear INTERNALS
This manual documents how to run and install the GNU compiler,
as well as its new features and incompatibilities, and how to report
-bugs. It corresponds to GNU CC version 2.7.2.
+bugs. It corresponds to EGCS version 1.0.
@end ifclear
@ifclear USING
This manual documents how to port the GNU compiler,
as well as its new features and incompatibilities, and how to report
-bugs. It corresponds to GNU CC version 2.7.1.
+bugs. It corresponds to EGCS version 1.0.
@end ifclear
@end ifinfo
projects / thirdparty / gcc.git / commitdiff
