incubator-stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Black (JIRA)" <j...@apache.org>
Subject [jira] Updated: (STDCXX-254) runall.sh incorrectly invoks test suite executables
Date Fri, 07 Jul 2006 20:23:30 GMT
     [ http://issues.apache.org/jira/browse/STDCXX-254?page=all ]

Andrew Black updated STDCXX-254:
--------------------------------

    Attachment: xopsfix.diff

Attached is a (2 line) fix that should resolve this problem.

The --compat option is added to the RUNFLAGS in GNUmakefile.tst (--compat causes problems
for building locales if unconditionally included)

The contents of the $XOPTS shell variable is moved prior to the hardcoded options used when
invoking child processes in the runall.sh script (needed so that --compat is passed prior
to -O for test suite executables)

> runall.sh incorrectly invoks test suite executables
> ---------------------------------------------------
>
>          Key: STDCXX-254
>          URL: http://issues.apache.org/jira/browse/STDCXX-254
>      Project: C++ Standard Library
>         Type: Bug

>   Components: Build
>  Environment: All
>     Reporter: Andrew Black
>  Attachments: xopsfix.diff
>
> When the run_all.sh script runs a test suite executable, the command used is similar
to
> ./25.partitions -O ./25.partitions.out -L 183 -M " Linux quandry 2.6.14.5 #1 PREEMPT
Thu Dec 29 16:01:39 MST 2005 i686 unknown unknown GNU/Linux " -C gcc-3.2.3 > ./25.partitions.out
< /dev/null 2>/dev/null &
> The problem with this invokation is that the test suite driver issues the following error
message on standard error:
> error: -O: option available only in compatibility mode
> The solution to this problem is to alter the run_all.sh script to pass --compat as an
option to the test prior to passing -O, but this causes problems with the run_locale_utils.sh
script.  In particular, this script doesn't understand the --compat option, and terminates
with a status of 1 as a result.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message