Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: domain of AntonP@moscow.vdiweb.com
 designates 195.210.189.132 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [jira] Updated: (STDCXX-202) [Windows] failed config tests
 labeled "ok"
Date: Fri, 16 Jun 2006 19:19:31 +0400
Message-ID: <4D6A8407B7AC6F4D95B0E55C4E7C4C6204689276@exmsk.moscow.vdiweb.com>
Thread-Topic: [jira] Updated: (STDCXX-202) [Windows] failed config tests
 labeled "ok"
Thread-Index: AcaP6jMy/IHaKhUHTduPfZq4en8YVABaxS8w
From: "Anton Pevtsov" <AntonP@moscow.vdiweb.com>
To: <stdcxx-dev@incubator.apache.org>

Martin, here is the fix to this bug:
http://people.apache.org/~antonp/stdcxx06162006/scripts/


With best wishes,
Anton Pevtsov


-----Original Message-----
From: Martin Sebor (JIRA) [mailto:jira@apache.org]=20
Sent: Wednesday, June 14, 2006 23:38
To: stdcxx-dev@incubator.apache.org
Subject: [jira] Updated: (STDCXX-202) [Windows] failed config tests
labeled "ok"


     [ http://issues.apache.org/jira/browse/STDCXX-202?page=3Dall ]

Martin Sebor updated STDCXX-202:
--------------------------------

    Attachment: log.text

The full log file is attached.

> [Windows] failed config tests labeled "ok"
> ------------------------------------------
>
>          Key: STDCXX-202
>          URL: http://issues.apache.org/jira/browse/STDCXX-202
>      Project: C++ Standard Library
>         Type: Bug

>   Components: Configuration
>     Versions: 4.1.3
>  Environment: Windows
>     Reporter: Martin Sebor
>     Assignee: Anton Pevtsov
>     Priority: Trivial
>  Attachments: log.text
>
> The Windows configuration infrastructure incorrectly labels some=20
> failled tests as passing (i.e., "ok"). The labeling should be
consistent across all config tests (i.e., "ok" when a test passes and
"no (<macro-name>)" when it fails; <macro-name> is the name of the macro
that is #defined in response to the failure; it should be enclosed in
parentheses and the whole thing separated from the word "no" by a single
space).
> ------ Build started: Project: .configure, Configuration: 15d Debug
Thread-safe=20
> Dll Win32 ------
> Performing Custom Build Step
> Microsoft (R) Windows Script Host Version 5.6
> Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
> Configuring for msvc-7.1 - 15d Debug Thread-safe Dll
> Checking if compiler is sane...   ok
> Checking if linker is sane...   ok
> Checking if run environment is sane...   ok
> Checking system architecture ILP32 little endian
> Checking for headers...=20
> ...
> Checking for <ieeefp.h>...  no (_RWSTD_NO_IEEEFP_H)
> Checking for <pthread.h>...  no (_RWSTD_NO_PTHREAD_H)
> Checking for namespaces  ok
> ...
> Checking for std::vsprintf() in <cstdio>...   ok
> Checking for std::snprintf() in <cstdio>...  no _RWSTD_NO_SNPRINTF
> ...
> checking for atomic operations...   ok=20
> checking for bad_alloc copy ctor...   ok _RWSTD_NO_BAD_ALLOC_COPY_CTOR
> checking for bad_alloc default ctor...   ok
_RWSTD_NO_BAD_ALLOC_DEFAULT_CTOR
> checking for bad_alloc dtor...   ok _RWSTD_NO_BAD_ALLOC_DTOR
> checking for bad_alloc::what()...   ok _RWSTD_NO_BAD_ALLOC_WHAT
> ...

--=20
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