Hi

Had downloaded GCC-2.95.2 from egcs.cygnus.com on Nov 1 After geting GPC working made original post on what I did Here's some supplimentry information which might help clear the air:

An excerpt from: "Installing GCC: Configuration" Quote:

We use _srcdir_ to refer to the toplevel source directory for GCC; we use _objdir_ to refer to the toplevel build/object directory.

First, we _highly_ recommend that GCC be built into a separate directory than the sources which does _not_ reside within the source tree. This is how we generally build GCC; building where _srcdir_ == _objdir_ should still work, but doesn't get extensive testing; ...

To configure GCC:

% mkdir _objdir_ % cd _objdir_ % _srcdir_/configure _[target]_ _[options]_

Use _options_ to override several configure time options for GCC. A partial list of supported options: * --enable-languages=_lang1_,_lang2_,... -- Specify that only a particular subset of compilers and their runtime libraries should be built. For a list of valid values for _lang_x you can issue the following command in the gcc directory of your GCC source tree: grep language= */config-lang.in Currently, you can use any of the following: CHILL, c++, f77, java and objc. Please note, that this switch does not work with EGCS 1.1.2 or older versions of egcs. It will be supported in GCC 2.95 and newer version. If you do not pass this flag, all languages available in the gcc sub-tree will be configured. Re-defining LANGUAGES when calling make bootstrap _*does not*_ work anymore, as those language sub-directories might not have been configured!

_Last modified on July 16, 1999._ Unquote

BTW, discovered once you run configure you can't run it again until you either erase certain file(s) in _objdir_ or use a different _objdir_

An excerpt from: "Installing GCC: Building" Quote

Building a native compiler

For a native build issue the command `make bootstrap'. This will build the entire GCC 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 binutils (bfd, binutils, gas, gprof, ld, and opcodes) if they have been individually linked or moved into the top level GCC source tree before configuring. * 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 used the flag --enable-languages=... to restrict the compilers to be built, only those you've actually enabled will be built. This will of course only build those runtime libraries, for which the particular compiler has been built. Please note, that re-defining LANGUAGES when calling `make bootstrap' _*does not*_ work anymore!

_Last modified on August 27, 1999._ Unquote

One last note: after installation GCC now reports same new version as GPC, cc reports the original version that was installed here