This is the mail archive of the
gcc-testresults@gcc.gnu.org
mailing list for the GCC project.
Re: help .. bad email address in my reports
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.
A quick experiment shows this is promising. I added a line to the top
level Makefile to
pass CONFIG_LANGUAGES to the gcc/Makefile. Manually I confirmed that
the i960 fortran linking problem I have reported (c_lex undefined
PR3179) also
applied to java (make CONFIG_LANGUAGES="java").
I am getting ready to call it a weekend but this looks promising and may
let me
produce test results for secondayr languages even if one fails.
>
--
--
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