You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stdcxx.apache.org by "Martin Sebor (JIRA)" <ji...@apache.org> on 2006/06/14 21:37:30 UTC
[jira] Created: (STDCXX-202) [Windows] failed config tests labeled
"ok"
[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
Assigned to: Anton Pevtsov
Priority: Trivial
Attachments: log.text
The Windows configuration infrastructure incorrectly labels some 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
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...
...
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
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
...
--
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
[jira] Updated: (STDCXX-202) [Windows] failed config tests labeled
"ok"
Posted by "Martin Sebor (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/STDCXX-202?page=all ]
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 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
> 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...
> ...
> 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
> 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
> ...
--
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
[jira] Closed: (STDCXX-202) [Windows] failed config tests labeled
"ok"
Posted by "Martin Sebor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STDCXX-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Sebor closed STDCXX-202.
-------------------------------
> [Windows] failed config tests labeled "ok"
> ------------------------------------------
>
> Key: STDCXX-202
> URL: https://issues.apache.org/jira/browse/STDCXX-202
> Project: C++ Standard Library
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 4.1.3
> Environment: Windows
> Reporter: Martin Sebor
> Assigned To: Anton Pevtsov
> Priority: Trivial
> Fix For: 4.2
>
> Attachments: log.text
>
>
> The Windows configuration infrastructure incorrectly labels some 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
> 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...
> ...
> 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
> 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
> ...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (STDCXX-202) [Windows] failed config tests labeled
"ok"
Posted by "Farid Zaripov (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/STDCXX-202?page=all ]
Farid Zaripov resolved STDCXX-202.
----------------------------------
Fix Version/s: 4.2
Resolution: Fixed
Fixed thus: http://svn.apache.org/viewvc?rev=414852&view=rev
> [Windows] failed config tests labeled "ok"
> ------------------------------------------
>
> Key: STDCXX-202
> URL: http://issues.apache.org/jira/browse/STDCXX-202
> Project: C++ Standard Library
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 4.1.3
> Environment: Windows
> Reporter: Martin Sebor
> Assigned To: Anton Pevtsov
> Priority: Trivial
> Fix For: 4.2
>
> Attachments: log.text
>
>
> The Windows configuration infrastructure incorrectly labels some 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
> 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...
> ...
> 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
> 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
> ...
--
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