This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Accept blanks as language separators
- To: manfred dot h at gmx dot net
- Subject: Re: Accept blanks as language separators
- From: Marc Espie <espie at quatramaran dot ens dot fr>
- Date: Tue, 1 Aug 2000 17:47:36 +0200
- Cc: gcc-patches at gcc dot gnu dot org
- Organization: Ecole Normale Superieure (quatramaran)
- References: <or4s55127l.fsf@guarana.lsd.ic.unicamp.br>
In article <14726.59927.366516.930897@saturn.hollstein.net> you write:
>On , 1 August 2000, 11:32:46 -0300, aoliva@redhat.com wrote:
>
>> Marc Espie was using blanks instead of commas as language separators,
>> so CXX_FOR_TARGET failed to be configured properly. This patch fixes
>> this problem. Ok to install?
>
>You also need to reflect this in gcc/configure.in then. Currently,
>the check there looks like this:
Actually, I've been using the older LANGUAGES instead of enable_languages,
which traditionally used whitespace as separator...
(and I've just switch to --enable-languages as well).
The question is more whether ${LANGUAGES} support should be completed or
removed completely.
Right now, we have the worst possible case, since it tends to be accepted, and
fails spectacularly in non-obvious ways later...