problems compiling gcc package on SunOS 4.1.4

[Phil Edwards]

On Sun, Oct 21, 2001 at 10:12:42PM -0500, Robert Bonomi wrote:
> 0) the README/INSTALL are excoriable, when it comes to what the components 
>     of the package are, and how to compile/install a -single- component,
>     or a selected subset.  a _simple_ list of the primary targets in the
>     main Makefile would be *extremely* helpful. The makefiles have so much
>     parameterization, etc. that it is *not* immediately obvious, even from
>     reading the Makefile itself.

In my copy of the gcc-3.0 package, the INSTALL directory contains complete
installation instructions in HTML.  From your mail it appears that you
skipped them entirely.  Were they not present in the package you downloaded?
If not, then there may be a packaging bug somewhere, but plenty of others
seem to have built 3.0.x successfully.


>     related: it would be very useful to have one-line descriptions of what
>     each first-level subdirectory is.  Would facilitate trimming the list
>     of directories to process, when one doe _not_ want "everything, including
>     the kitchen sink".

The directories are not meant to be trimmed.  If you don't want
certain things (you didn't say what), then you probably need to be
passing --enable/--disable flags to the configure script.  Probably
'--enable-languages=c' to start with.  For more information, see the
"Configuration" step in the installation instructions.


>   comment: $diety only knows why just typing 'make' tries to build this
>            *FIRST*, _before_ even building the new compiler!  you don't
>            need _this_ to compile the compiler, right?

"just typing make" is the wrong thing to do.  For more information, see the
"Building" step in the installation instructions.


>     b) compilation bombs, reference to "../gcc/{foo}", when the gcc directory
>        is _two_ levels up.

You definitely skipped reading the instructions.  Re-read the "Building"
step, especially the part about building in a separate directory from
the sources.  (This is tweaked in 3.0.2.)


>      Fortunately, I don't particularly need C++ compilation 
>      capabilities at this time.

You can list individual languages for which a compiler should be built.
If you only need C, then only enable C.


Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams