Re: rfc: new libgcc build mechanism

[Mark Mitchell <mark at codesourcery dot com>]

>>>>> "Richard" == Richard Henderson <rth@cygnus.com> writes:

    Richard> On Tue, May 02, 2000 at 01:45:55AM -0700, Mark Mitchell
    Richard> wrote:
    >> What's confusing me is that the set of languages for which the
    >> compiler is being built is known at configure-time, so that
    >> can't be the problem.

    Richard> Well, kinda.  To-date we've allowed LANGUAGES to be
    Richard> overridden on the make command line.

Oh, we have, have we. :-) I think that's a little weird.  All the
passing of flags down from the top-level to lower levels could be
eliminated in favor of configure actually scribbling the known right
values.

(For instance, it's pretty odd that doing a `make' in the gcc directory
has notable different behavior than doing a `make' in the toplevel
directory which then recurses into the gcc directory.  On IRIX, for
example, the former doesn't work at all; we try to build with
different ABIs depending on where we run make.)

If we can do away with the ability to override LANGUAGES on the
command-line, then configure can solve the problem it was designed to
solve: to automatically generate makefiles.

I wasn't sure if you were saying that the overriding of LANGUAGES is
necessary for some aspect of the bootstrap, or if you just didn't want
to kill it.  Do we need to keep this behavior, or can we kill it?

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com