[
https://issues.apache.org/jira/browse/STDCXX-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552841
]
Farid Zaripov commented on STDCXX-675:
--
Yes. This change doesn't affect the exported symbols or anything else.
[
https://issues.apache.org/jira/browse/STDCXX-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552871
]
Farid Zaripov commented on STDCXX-459:
--
1. This change is not necessary (and even more, it's incorrect, because
[
https://issues.apache.org/jira/browse/STDCXX-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor updated STDCXX-524:
Severity: Runtime Error
Summary: buffer overflow in test 22.locale.time.get.cpp (make_LC_TIME)
[
https://issues.apache.org/jira/browse/STDCXX-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Travis Vitek updated STDCXX-240:
Attachment: (was: stdcxx-240.patch)
#define _RWSTD_NO_EXCEPTIONS when exceptions are disabled
[
https://issues.apache.org/jira/browse/STDCXX-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Travis Vitek updated STDCXX-240:
Attachment: stdcxx-240.patch
2007-12-18 Travis Vitek [EMAIL PROTECTED]
STDCXX-240
[
https://issues.apache.org/jira/browse/STDCXX-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Travis Vitek closed STDCXX-676.
---
Resolution: Fixed
[MSVC] 22.locale.time.put test fails
Test suite and example programs don't compile on platforms that don't support
exceptions
Key: STDCXX-681
URL: https://issues.apache.org/jira/browse/STDCXX-681
2007-12-18 Travis Vitek [EMAIL PROTECTED]
* tests/src/printf.cpp (rw_snprintf): Add null terminator to
end of copied string to be compatible with sprintf.
--
View this message in context:
[
https://issues.apache.org/jira/browse/STDCXX-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Travis Vitek closed STDCXX-664.
---
Resolution: Fixed
Test passing automated testing.
[IBM XLC++ 9.0/AIX 5.3] SIGABRT in
[
https://issues.apache.org/jira/browse/STDCXX-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Travis Vitek closed STDCXX-614.
---
Resolution: Fixed
Verified in automated testing.
[gcc 4.1/Linux] error on size_t in
[
https://issues.apache.org/jira/browse/STDCXX-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552933
]
Travis Vitek commented on STDCXX-675:
-
If the new user takes advantage of the autolinking feature, they will
move build result pages from ~sebor to the stdcxx site
--
Key: STDCXX-682
URL: https://issues.apache.org/jira/browse/STDCXX-682
Project: C++ Standard Library
Issue Type: Task
Martin Sebor wrote:
This has been bugging me -- when someone checks out trunk, does a build
and sends
us build results, we have no way of telling that the build results are, in
fact, for trunk and
not for 4.2.0 (or the head of 4.2.x), because the value of _RWSTD_VER is
the same. I
Travis Vitek wrote:
Martin Sebor wrote:
This has been bugging me -- when someone checks out trunk, does a build
and sends
us build results, we have no way of telling that the build results are, in
fact, for trunk and
not for 4.2.0 (or the head of 4.2.x), because the value of _RWSTD_VER is
the
implement notion of expected failures in the test suite
---
Key: STDCXX-683
URL: https://issues.apache.org/jira/browse/STDCXX-683
Project: C++ Standard Library
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/STDCXX-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor updated STDCXX-684:
Summary: auto-detect _RWSTD_VER value from branch/file name (was:
ato-detect _RWSTD_VER value
I was recently asked how to go about getting a forgotten password
reset. I thought I'd post the answer(s) here in case someone needs
this info in the future:
If you forgot you svn password here's an FAQ that might help:
http://www.apache.org/dev/committers.html#svn-authorization-failure
[
https://issues.apache.org/jira/browse/STDCXX-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Travis Vitek updated STDCXX-605:
Attachment: (was: stdcxx-605.patch)
[IBM XLC++] errors compiling dynatype.cpp
[
https://issues.apache.org/jira/browse/STDCXX-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Travis Vitek updated STDCXX-605:
Attachment: stdcxx-605-v2.patch
stdcxx-605-v1.patch
In the failure you mention,
[
https://issues.apache.org/jira/browse/STDCXX-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553208
]
vitek edited comment on STDCXX-605 at 12/18/07 6:49 PM:
---
In the failure you mention,
[
https://issues.apache.org/jira/browse/STDCXX-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Travis Vitek updated STDCXX-605:
Attachment: stdcxx-605-out.patch
The update output is now attached as a separate patch.
[IBM
Martin Sebor wrote:
Travis Vitek wrote:
Martin Sebor wrote:
This has been bugging me -- when someone checks out trunk, does a build
and sends
us build results, we have no way of telling that the build results are,
in
fact, for trunk and
not for 4.2.0 (or the head of 4.2.x),
Travis Vitek wrote:
Martin Sebor wrote:
Travis Vitek wrote:
Martin Sebor wrote:
This has been bugging me -- when someone checks out trunk, does a build
and sends
us build results, we have no way of telling that the build results are,
in
fact, for trunk and
not for 4.2.0 (or the head of
23 matches
Mail list logo
