Re: help .. bad email address in my reports

[Joel Sherrill <joel at OARcorp dot com>]

Alexandre Oliva wrote:

> On Jul 24, 2001, Joel Sherrill <joel.sherrill@OARcorp.com> wrote:
> 
>> I would like to tinker with my build/test script to 
>> cover more languages.  But right now, many fail in
>> one specific language.  Is there a way to do this?
> 
> 
> I'm afraid not.  make LANGUAGES="..." is deprecated in favor of
> --enable-languages, and, even if it weren't, if it completed, you'd
> get everything built supporting the selected set of LANGUAGES.  Then,
> if you changed LANGUAGES, you wouldn't get everything build to extend
> that set.  The most important example used to be the C++ support
> routines in libgcc... Hmm, but these are in libstdc++/libsupc++ now,
> so perhaps it would work now.  A quick analysis of the Makefiles
> indicates it probably would.  You may want to set CONFIG_LANGUAGES,
> instead of just LANGUAGES, though.  I don't know.  Perhaps you could
> give it a try and report back if it doesn't?  This would be definitely
> useful in the case you point out, even though it probably isn't
> something we'd like to support for end users.
> 
I have tried overriding CONFIG_LANGUAGES to build the languages individually
with C first.  This seems to work kind of OK but configuring with C++ 
enabled
apparently enables libstdc++-v3 in such a way that a command line 
override of
CONFIG_LANGUAGES does not take it out of the build.  So a configure
of C/C++ followed by a make CONFIG_LANGUAGES="c" results in
the build dying when libstdc++-v3 can't find the target C++ compiler.

If you get past that, it works great.  On at least one target, 2 of the
languages failed to build but this let the others build.

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel@OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985