--- /dev/null
+Building egcs-1.00
+
+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.
+
+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:
+
+ * 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.
+
+ * Perform a 3-stage bootstrap of the compiler.
+
+ * Perform a comparison test of the stage2 and stage3 compilers.
+
+ * 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
+
+We recommend reading the crossgcc FAQ for information about building cross
+compilers. (ftp.cygnus.com:pub/crossgcc)
+
+For a cross build, issue the command "make cross", which performs the
+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 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.
+
+
--- /dev/null
+Configuring egcs-1.00
+
+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.
+
+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.
+
+To configure egcs:
+
+ % 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.
+
+options specification
+
+Use options to override several configure time options for egcs. A partial list
+of supported options:
+
+ * --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.
+
+ * --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.
+
+ * --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.
+
+ * --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.
+
+ * --enable-multilib -- Specify that multiple libraries should be built
+ to support different target variants, calling conventions, etc. This is the
+ default.
+
+ * --enable-threads -- Specify that the target supports threads.
+ * --enable-threads=lib -- Specify that lib is the thread support
+ 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.
+
+
--- /dev/null
+Final install egcs-1.00
+
+Now that egcs has been built and tested, you can install it with
+"cd objdir; make install".
+
+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 srcdirconfig.guess.
+
+If you find a bug in egcs, please report it to egcs-bugs@cygnus.com.
+
+
+
--- /dev/null
+ Installing egcs-1.00
+
+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
+installation information in the source distribution for historical reference
+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.
+
+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.
+
+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).
--- /dev/null
+This directory contains installation instrutions for egcs-1.00.
+
+We're providing installation instructions in two forms, html and
+plaintext.
+
+index.html is the toplevel install file for html browsers.
+
+INDEX is the toplevel install file in plaintext form.
+
+The most recent HTML installation instructions for egcs can be obtained from
+the egcs web site:
+
+http://www.cygnus.com/egcs/install
+
--- /dev/null
+Host/Target specific installation notes for
+ egcs-1.00
+
+alpha*-*-*
+No specific installation needs/instructions.
+
+i?86-*-linux-gnulibc1
+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.
+Look in gcc/config/i386/sco5.h (search for "messy") for additional
+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.
+
+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
+linker crashes in some circumstances; the workarounds also probably prevent
+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.
+
+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
+
+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
+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".
+
+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.
+
+cd objdir
+make all-texinfo all-bison all-byacc all-binutils all-gas all-ld
+cd gcc
+make bootstrap
+make install-headers-tar
+cd ..
+make bootstrap3
+
+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.
+
+
+You may get the following warning on irix4 platforms, it can be safely
+ignored.
+
+ warning: foo.o does not have gp tables for all its sections.
+
+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.*.
+
--- /dev/null
+Testing egcs-1.00
+
+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.
+
+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.
+
+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.
+
+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.
+
--- /dev/null
+<html>
+<head>
+<title>Building egcs-1.00 </title>
+</head>
+<body bgcolor="white">
+<h1 align="center">Building egcs-1.00</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>For a native build issue the command "make bootstrap". This will build
+the entire egcs compiler system, which includes the following steps:
+
+<ul>
+ <li> Build host tools necessary to build the compiler such as texinfo, bison,
+ gperf.<p>
+
+ <li> Build target tools for use by the compiler such as gas, gld, and
+ binutils.<p>
+
+ <li> Perform a 3-stage bootstrap of the compiler.<p>
+
+ <li> Perform a comparison test of the stage2 and stage3 compilers.<p>
+
+ <li> Build runtime libraries using the stage3 compiler from the previous
+ step.<p>
+</ul>
+
+<p>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.
+
+<b>Building a cross compiler</b>
+
+<p> We recommend reading the
+<a href="ftp://ftp.cygnus.com/pub/embedded/crossgcc/FAQ-0.8.1">
+crossgcc FAQ</a> for information about building cross compilers.
+
+<p>For a cross build, issue the command "make cross", which performs the
+following steps:
+<ul>
+ <li> Build host tools necessary to build the compiler such as texinfo, bison,
+ gperf.<p>
+
+ <li> Build target tools for use by the compiler such as gas, gld, and
+ binutils.<p>
+
+ <li> Build the compiler (single stage only).<p>
+
+ <li> Build runtime libraries using the compiler from the previous
+ step.<p>
+</ul>
+
+<p>Note that if an error occurs in any step the make process will exit.
+
+<p>
+<hr>
+<i>Last modified on December 1, 1997.</i>
+
+</body>
+</html>
--- /dev/null
+<html>
+<head>
+<title>Configuring egcs-1.00 </title>
+</head>
+<body bgcolor="white">
+<h1 align="center">Configuring egcs-1.00</h1>
+
+<p>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.
+
+<p>We use <i>srcdir</i> to refer to the toplevel source directory for
+egcs; we use <i>objdir</i> to refer to the toplevel build/object
+directory for egcs.
+
+<p>First, we <b>highly</b> recommend that egcs be built into a separate
+directory than the sources. This is how we generally build egcs; building
+where <i>srcdir</i> == <i>objdir</i> should still work, but doesn't get
+extensive testing.
+
+<p>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.
+
+<p>To configure egcs:
+
+<blockquote>
+<tt>
+ <br>% mkdir <i>objdir</i>
+ <br>% cd <i>objdir</i>
+ <br>% <i>srcdir</i>/configure <b>[target]</b> <b>[options]</b>
+</tt>
+</blockquote>
+
+
+<p><b>target specification</b>
+<ul>
+ <li> egcs has code to correctly determine the correct value for
+ <b>target</b> for nearly all native systems. Therefore, we highly
+ recommend you not provide a configure target when configuring a
+ native compiler.
+
+ <li> <b>target</b> must be specified when configuring a cross compiler;
+ examples of valid targets would be i960-rtems, m68k-coff, sh-elf, etc.
+</ul>
+
+
+<p><b> options specification</b>
+
+<p>Use <b>options</b> to override several configure time options for
+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.
+
+ <br>These additional options control where certain parts of the distribution
+ are installed. Normally you should not need to use these options.
+ <ul>
+ <li> <tt>--with-local-prefix=</tt><i>dirname</i> -- Specify the installation
+ directory for local include files. The default is /usr/local.
+
+ <li> <tt>--with-gxx-include-dir=</tt><i>dirname</i> -- Specify the installation
+ 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-haifa</tt> -- Enable the new Haifa instruction scheduler in the
+ compiler; the new scheduler can significantly improve code on some targets.
+ <tt>--disable-haifa</tt> is currently the default on all platforms except the HPPA.
+
+ <li> <tt>--with-gnu-as</tt> -- Specify that the compiler should assume the GNU
+ assembler (aka gas) is available.
+
+ <li> <tt>--with-gnu-ld</tt> -- Specify that the compiler should assume the GNU
+ linker (aka gld) is available.
+
+ <li> <tt>--with-stabs</tt> -- 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.
+
+ <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-threads</tt> -- Specify that the target supports threads.
+
+ <li> <tt>--enable-threads=</tt><i>lib</i> -- Specify that <i>lib</i> is the thread
+ support 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
+ RS6000/PowerPC ports.
+</ul>
+
+<p>Some options which only apply to building cross compilers:
+<ul>
+ <li> <tt>--with-headers=</tt><i>dir</i> -- Specifies a directory which has target
+ include files.
+ <li> <tt>--with-libs=</tt><i>dirs</i> -- Specifies a list of directories which contain
+ the target runtime libraries.
+ <li> <tt>--with-newlib</tt> -- 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.
+</ul>
+
+<p>Note that each <tt>--enable</tt> option has a corresponding <tt>--disable</tt> option and
+that each <tt>--with</tt> option has a corresponding <tt>--without</tt> option.
+
+
+<p>
+<hr>
+<i>Last modified on December 1, 1997.</i>
+
+</body>
+</html>
--- /dev/null
+<html>
+<head>
+<title>Final install egcs-1.00 </title>
+</head>
+<body bgcolor="white">
+<h1 align="center">Final install egcs-1.00</h1>
+
+<p>Now that egcs has been built and tested, you can install it with
+"cd <i>objdir</i>; make install".
+
+<p>That step completes the installation of egcs; user level binaries can
+be found in <i>prefix</i>/bin where <i>prefix</i> is the value you specified
+with the --prefix to configure (or /usr/local by default).
+
+<p>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 <i>srcdir</i>config.guess.
+
+<p>If you find a bug in egcs, please report it to
+<a href="mailto:egcs-bugs@cygnus.com">egcs-bugs@cygnus.com</a>.
+
+<p>
+<hr>
+<i>Last modified on December 1, 1997.</i>
+
+</body>
+</html>
--- /dev/null
+<html>
+<head>
+<title>Installing egcs-1.00 </title>
+</head>
+<body bgcolor="white">
+<h1 align="center">Installing egcs-1.00</h1>
+
+<p>This document describes the generic installation procedure for egcs as
+well as detailing some target specific installation instructions for egcs.
+
+<p>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
+installation information in the source distribution for historical reference
+purposes only.
+
+<p>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.
+
+<p>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
+<a href="../faq.html">FAQ</a> to see if your problem is covered before you file
+a bug report.
+
+<p>The installation procedure is broken into four steps.
+
+<ul>
+
+ <li> <a href="configure.html">configure</a>
+ <li> <a href="build.html">build</a>
+ <li> <a href="test.html">test</a> (optional)
+ <li> <a href="finalinstall.html">install</a>
+
+</ul>
+
+<p>Before starting the build/install procedure <b>please</b> browse the
+<a href="specific.html">host/target specific installation notes</a>.
+
+<hr>
+<a href="../index.html">Return to the egcs home page</a>
+</body>
+</html>
+<hr>
+<i>Last modified on December 1, 1997.</i>
+
--- /dev/null
+<html>
+<head>
+<title>Host/Target specific installation notes for egcs-1.00 </title>
+</head>
+<body bgcolor="white">
+<h1 align="center">Host/Target specific installation notes for egcs-1.00</h1>
+
+<p><b>alpha*-*-*</b><br>
+No specific installation needs/instructions.
+
+
+<p><b>i?86-*-linux-gnulibc1</b><br>
+You will need binutils-2.8.1.0.15 or newer for exception handling to work.
+
+<p><b>i?86-*-sco3.2v5*</b><br>
+The SCO assembler is currently required. The GNU assembler is not up
+to the task of switching between ELF and COFF at runtime.
+
+<br>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.
+
+<br>Look in gcc/config/i386/sco5.h (search for "messy") for additional
+OpenServer-specific flags.
+
+
+
+<p><b>hppa*-hp-hpux*</b><br>
+We <b>highly</b> 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.
+
+<p><b>hppa*-hp-hpux9</b><br>
+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.
+
+<br>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.
+
+<p><b>hppa*-hp-hpux10</b><br>
+For hpux10.20, we <b>highly</b> recommend you pick up the latest sed
+patch from HP. HP has two sites which provide patches free of charge.
+
+<br><a href="http://us-support.external.hp.com">US, Canada, Asia-Pacific, and
+Latin-America</a>
+<br><a href="http://europe-support.external.hp.com">Europe</a>
+
+<p>Retrieve patch PHCO_12862.
+
+<p>The HP assembler on these systems is much better than the hpux9 assembler,
+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".
+
+<p><b>m68k-*-nextstep*</b><br>
+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.
+<p>cd <i>objdir</i><br>
+make all-texinfo all-bison all-byacc all-binutils all-gas all-ld<br>
+cd gcc<br>
+make bootstrap<br>
+make install-headers-tar<br>
+cd ..<br>
+make bootstrap3<br>
+
+<p><b>mips*-sgi-irix4</b><br>
+<p><b>mips*-sgi-irix5</b><br>
+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.
+
+<p>You may get the following warning on irix4 platforms, it can be safely
+ignored.
+<pre>
+ warning: foo.o does not have gp tables for all its sections.
+</pre>
+
+<p><b>powerpc-*-linux-gnu*</b><br>
+You will need
+<a href="ftp://ftp.yggdrasil.com/private/hjl">binutils-2.8.1.0.17</a> for
+a working egcs. It is strongly recommended to recompile binutils with egcs
+if you initially built it with gcc-2.7.2.*.
+
+<p>
+exception handling
+<p>XXX Linux stuff
+-k encaps stuff
+<hr>
+<i>Last modified on December 1, 1997.</i>
+
+</body>
+</html>
--- /dev/null
+<html>
+<head>
+<title>Testing egcs-1.00 </title>
+</head>
+<body bgcolor="white">
+<h1 align="center">Testing egcs-1.00</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>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.
+
+<p>Second, you must have a new version of dejagnu on your system; dejagnu-1.3
+will not work. We have made a
+<a href="ftp://ftp.cygnus.com/pub/egcs/infrastructure/dejagnu-971028.tar.gz">
+dejagnu snapshot</a> available in ftp.cygnus.com:/pub/egcs/infrastructure until
+a new version of dejagnu can be released.
+
+<p>Assuming you've got the testsuites unpacked and have installed an appropriate
+dejagnu, you can run the testsuite with "cd <i>objdir</i>; make -k check".
+This may take a long time. Go get some lunch.
+
+<p>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.
+
+<p> How to interpret test results XXX.
+
+<hr>
+<i>Last modified on December 1, 1997.</i>
+
+</body>
+</html>
projects / thirdparty / gcc.git / commitdiff
