This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: rfc: new libgcc build mechanism
- To: kenner at vlsi1 dot ultra dot nyu dot edu
- Subject: Re: rfc: new libgcc build mechanism
- From: Mark Mitchell <mark at codesourcery dot com>
- Date: Tue, 02 May 2000 08:55:26 -0700
- Cc: gcc-patches at gcc dot gnu dot org
- Organization: CodeSourcery, LLC
- References: <10005021541.AA22644@vlsi1.ultra.nyu.edu>
>>>>> "Richard" == Richard Kenner <kenner@vlsi1.ultra.nyu.edu> writes:
Richard> Well, we're going to keep it for now, anyhow. But
Richard> why not just use --enable-languages? That's what it's
Richard> for.
Richard> Because that means I have to re-run configure and it
Richard> changes my directories. Many times all I want to do is
Richard> just build some languages, leaving everything else alone
Richard> (including the old binaries of the other languages).
So, in that case, if I understand everything, Richard's scheme might
actually do the wrong thing; you don't want libgcc to suddenly contain
different functions. Instead, libgcc should be rebuilt using whatever
languages you specified with --enable-languages at configure time.
Basically, it doesn't make sense to use the same thing to say what
languages you want to build *right now* and what languages you want to
build ever in this tree.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com