Farid Zaripov wrote:
-Original Message-
From: Martin Sebor [mailto:[EMAIL PROTECTED]
Sent: Friday, October 19, 2007 7:40 PM
To: stdcxx-dev@incubator.apache.org
Subject: Re: svn commit: r586502 -
/incubator/stdcxx/branches/4.2.0/include/rw/_config-msvcrt.h
I think we can also
Farid Zaripov wrote:
-Original Message-
From: Martin Sebor [mailto:[EMAIL PROTECTED]
Sent: Friday, October 19, 2007 6:51 PM
To: stdcxx-dev@incubator.apache.org
Subject: Re: svn commit: r586502 -
/incubator/stdcxx/branches/4.2.0/include/rw/_config-msvcrt.h
I take it this is necessary
I'm getting ready to commit the original patch -- Travis,
do you agree? Farid, any concerns or comments with it?
Martin
Martin Sebor wrote:
Travis Vitek wrote:
Martin,
That patch won't work. The _C_grow needs to be made private. It was
private in 4.1.3, but is public in 4.2. IMO it should
Okay, unless I hear further objections in the next 10 minutes
or so this is going in.
Martin
Travis Vitek wrote:
Martin Sebor wrote:
Travis Vitek wrote:
The only thing I don't like about this patch is that it
assumes no other platform will exhibit the same behavior
that we are seeing
Thanks!
Farid, does this patch look okay to you?
Travis, please double-check the patch for missing whitespace
and post a ChangeLog entry. Unless there are objections from
Farid or anyone else, I'll go ahead and commit it as soon as
I get it.
Martin
Travis Vitek wrote:
This patch attempts to
[
https://issues.apache.org/jira/browse/STDCXX-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535937
]
Martin Sebor commented on STDCXX-162:
-
As noted in the following thread:
http://www.nabble.com/stdcxx-4.2.0
What is the status of the patch for the unsats for the exception
classes on Windows? Anyone working on it? Farid? Travis?
Martin
This is in, both on 4.2.0 and trunk:
http://svn.apache.org/viewvc?rev=586016view=rev
http://svn.apache.org/viewvc?rev=586017view=rev
Martin Sebor wrote:
Martin Sebor wrote:
This patch attempts to fix the binary incompatibility of __rw_facet
ctor and dtor when compiled with MSVC on Windows
_RWSTD_NO_EXCEPTION_DEFAULT_CTOR
#define _RWSTD_NO_EXCEPTION_DTOR
#define _RWSTD_NO_EXCEPTION_WHAT
-Original Message-
From: Martin Sebor [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 18, 2007 8:50 AM
To: stdcxx-dev@incubator.apache.org
Subject: status of fix for incompatibilities
).aspx
http://msdn2.microsoft.com/en-us/library/7977wcck(VS.80).aspx
Martin
Farid Zaripov wrote:
-Original Message-
From: Martin Sebor [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 18, 2007 5:43 PM
To: stdcxx-dev@incubator.apache.org
Subject: Re: [PATCH] __rw_dbl_infinity ABI change
to avoid. The purpose of the configuration
tests, i.e., to adjust the library to the compilation environment,
is at odds with goal of providing binary compatibility...
Martin Sebor wrote:
While testing the patch for the missing exception symbols I'm
running into a few other unsats that I haven't seen
While testing the patch for the missing exception symbols I'm
running into a few other unsats that I haven't seen mentioned
before. I'm not sure if it's relevant yet but I'm linking
stdcxx 4.2.0 15d DLL built with MSVC 8.0 into 4.1.3 examples
built with MSVC 7.1 (also 15d).
EXAMPLE
Travis Vitek wrote:
Travis Vitek wrote:
I totally forgot about it after scrambling to get the other patch made
last night. I'll post a patch for review ASAP.
Martin Sebor wrote:
What is the status of the patch for the unsats for the exception
classes on Windows? Anyone working
Farid Zaripov wrote:
From: Travis Vitek [mailto:[EMAIL PROTECTED]
Sent: Чт, 18.10.2007 22:59
To: stdcxx-dev@incubator.apache.org
Subject: RE: status of fix for incompatibilities in exception classes on Windows
That is fine.
2007-10-18 Travis Vitek [EMAIL PROTECTED]
* _config-msvc.h
Travis Vitek wrote:
Martin Sebor wrote:
Farid Zaripov wrote:
From: Travis Vitek wrote:
That is fine.
2007-10-18 Travis Vitek [EMAIL PROTECTED]
* _config-msvc.h [_RWSTD_VER_MAJOR]: Define configuration
macros to enable binary compatibility with 4.1.3 on MSVC.
I
Farid Zaripov wrote:
The binary compatibility requirement is related to shared libraries only,
or to both shared and static libraries?
Both.
When the user builds their own shared library, libusr.so, from
the stdcxx archive, libstd.a, (a subset of) stdcxx symbols become
part of the interface
I created what I'm hoping will be the final stdcxx 4.2.0 release
candidate, stdcxx-4.2.0-rc-6:
http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-6/
along with a tarball containing the sources:
http://people.apache.org/~sebor/stdcxx/stdcxx-incubating-4.2.0.tar.gz
The MD5 sum for the
[
https://issues.apache.org/jira/browse/STDCXX-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor closed STDCXX-509.
---
Resolution: Fixed
We can finally close this. Whew!
See this thread for background into the final
[
https://issues.apache.org/jira/browse/STDCXX-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor closed STDCXX-505.
---
Resolution: Fixed
Closing as fixed.
Update the Acknowledgments page
Are we making use of it? If not, should we be?
http://msdn2.microsoft.com/en-us/library/h88b7dc8(VS.80).aspx
Martin
Travis Vitek wrote:
Farid Zaripov wrote:
Since the patch was stripped, Im sending it inplace.
ChangeLog:
STDCXX-509
* limits_bits.cpp [_RWSTD_VER_MAJOR 5 _MSC_VER _DLL]:
The _xxxBits constants defined with C++ linkage and exported
as the floating constants with the mangled names
Farid, I'm afraid your patch got stripped -- can you try again,
maybe inline?
Martin
Farid Zaripov wrote:
From: Martin Sebor [mailto:[EMAIL PROTECTED]
Sent: Пт, 19.10.2007 0:35
To: stdcxx-dev@incubator.apache.org
Subject: Re: binary compatibility question
[...]
So what would we do
William A. Rowe, Jr. wrote:
Farid Zaripov wrote:
But personally for me the version in the version info resource
would be more interesting. BTW there are more fields, i.e.
Copyright, Product Name, Company Name, Description, ...
From your answer, I presume it's no.
I don't know for 100%
[
https://issues.apache.org/jira/browse/STDCXX-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor reassigned STDCXX-505:
---
Assignee: Martin Sebor (was: Marc Betz)
Update the Acknowledgments page
[
https://issues.apache.org/jira/browse/STDCXX-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor updated STDCXX-406:
Fix Version/s: (was: 4.2)
4.2.1
Unfortunately, this has to be deferred
FYI: I've compiled a 12d build of stdcxx 4.1.3 with Sun C++ 5.8
on Solaris 10 and, after replacing the stdcxx library with the
one from 4.2.0 (compiled with Sun C++ 5.9, also on Solaris 10),
run all examples, tests, and build the en_US.UTF-8 locale and
found no binary incompatibilities.
I'm
In a 12D build with the default gcc 4.1.0 on SuSE Linux Enterprise
Server 10 (x86_64), the following simple program abends with the
error below after upgrading the 4.1.3 library to 4.2.0:
#include string
int main ()
{
std::string s = a;
}
The only library symbols referenced from the
Travis Vitek wrote:
So I've been looking at the issue of the missing symbols for the
destructor, copy constructor and assignment operators for bad_cast,
bad_typeid and exceptions. Specifically, these symbols...
So based on the config macros below, 4.1.3 shouldn't have had
the definition of the
Travis Vitek wrote:
Martin Sebor wrote:
Travis Vitek wrote:
So I've been looking at the issue of the missing symbols for the
destructor, copy constructor and assignment operators for bad_cast,
bad_typeid and exceptions. Specifically, these symbols...
So based on the config macros below, 4.1.3
will break binary compatibility on the (now) most popular
platform.
Opinions?
Martin
Martin Sebor wrote:
Martin Sebor wrote:
In a 12D build with the default gcc 4.1.0 on SuSE Linux Enterprise
Server 10 (x86_64), the following simple program abends with the
error below after upgrading the 4.1.3
Travis Vitek wrote:
From: Martin Sebor [mailto:[EMAIL PROTECTED]
No, you've got it backwards. :) NO_BAD_CAST_ASSIGNMENT means
the function is not found in the runtime and that we need to
define it in the library. When the macro is not defined
(notice the double negative, !NO_XXX), the function
Travis, if you still have the email I sent you privately last night
with the links to the svn changes for the incompatibilities below,
can you pass those on? I can't access the email from where I am
right now and having the details might be helpful in deciding if
we should try to fix the problems
Mark Brown wrote:
On 10/17/07, Martin Sebor [EMAIL PROTECTED] wrote:
Okay, I've got it:
http://issues.apache.org/jira/browse/STDCXX-162
Damn that was hard!
So, what do we do? Going back to using a mutex for strings would
be *huge* performance hit on one of the most popular platforms
Farid Zaripov wrote:
Below is the difference in exported symbols between 4.1.3 and 4.2.0
15d dll's (MSVC 7.1).
I've removed the symbols, which appears in 4.2.0 dll but not exist in
4.1.3 dll.
To make the list easier to read I've replaced the long names with
their standard typedefs (and
[
https://issues.apache.org/jira/browse/STDCXX-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535754
]
Martin Sebor commented on STDCXX-142:
-
Following up on my comment above: *BUT*, since _C_grow() is a) inline
Versions: trunk
Environment: all
Reporter: Martin Sebor
Priority: Trivial
Fix For: 4.2.1
...the function is inline and only called from std::stringbuf::str(). Removing
it (by virtue of expanding its body into str()) will reduce the number of
symbols
[EMAIL PROTECTED]@[EMAIL PROTECTED]@std@@[EMAIL PROTECTED]@2@@std@@AB
[EMAIL PROTECTED]
tests/22.locale.num.put.exe [EMAIL PROTECTED]@@[EMAIL PROTECTED]
-Original Message-
From: Martin Sebor [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 17, 2007 1:44 PM
To: Travis Vitek
[
https://issues.apache.org/jira/browse/STDCXX-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535746
]
Martin Sebor commented on STDCXX-142:
-
As discussed in the thread below, the change to the signature of _C_grow
to not be
accessable to user code.
Ah, I know why! Because it's called from a member template which
gets instantiated in the test.
So we need to add string::_C_grow() to the list of symbols to
fix in 4.2.0.
Martin
Martin Sebor wrote:
From a private discussion (copied below) it sounds like the set
of real
This patch attempts to fix the binary incompatibility of __rw_facet
ctor and dtor when compiled with MSVC on Windows, introduced while
fixing STDCXX-469 (MSVC mangles the access specifier into the names
of class members):
https://issues.apache.org/jira/browse/STDCXX-469
I considered limiting
will not be inlined under some conditions but I expect
those to be exceeding rare.
Martin
Travis
Martin Sebor wrote:
Okay, I've got it:
http://issues.apache.org/jira/browse/STDCXX-162
Damn that was hard!
So, what do we do? Going back to using a mutex for strings would
be *huge
header by the user. This whole hackery
is guarded by _RWSTD_VER and automatically disabled (i.e.,
the library switches over to using atomic operations by
default) at version 5.
Martin
Martin Sebor wrote:
Travis Vitek wrote:
So the problem is that the size of the __string_ref has changed, right
to x86_64 in time for 4.1.3 (bad mistake):
http://issues.apache.org/jira/browse/STDCXX-162
Also, if you want to pick nits, the version check should probably use
_RWSTD_VER_MAJOR.
Yes, that would be better. I'll change it.
Martin
Travis
-Original Message-
From: Martin Sebor [mailto
Mark Brown wrote:
Martin Sebor wrote:
After dispatching the remaining issues scheduled for 4.2.0(*) I'd
like to merge the few outstanding minor fixes and docs changes to
4.2.0 and create the (hopefully) final release candidate at the
end of the day (US/Mountain) tomorrow. If anyone has any
created
the rest, I suppose I could generate it and remove those I added
to the subdirectories. Does that sound like the right approach
to everyone?
Martin
-- Mark
Martin Sebor wrote:
After I generated/updated the latest ChangeLogs I noticed that we have
been less than completely consistent
[EMAIL PROTECTED] wrote:
Author: ablack
Date: Tue Oct 16 06:54:59 2007
New Revision: 585143
URL: http://svn.apache.org/viewvc?rev=585143view=rev
Log:
2007-10-15 Andrew Black [EMAIL PROTECTED]
STDCXX-109
* etc/config/makefile.rules ($(CATFILE)): Make failure to execute
the
Farid Zaripov wrote:
-Original Message-
From: Farid Zaripov [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 16, 2007 5:39 PM
To: stdcxx-dev@incubator.apache.org
Subject: RE: 4.2.0-rc-6, final candidate
-Original Message-
From: Martin Sebor [mailto:[EMAIL PROTECTED]
Sent
Andrew Black wrote:
Martin Sebor wrote:
[EMAIL PROTECTED] wrote:
Author: ablack
Date: Tue Oct 16 06:54:59 2007
New Revision: 585143
URL: http://svn.apache.org/viewvc?rev=585143view=rev
Log:
2007-10-15 Andrew Black [EMAIL PROTECTED]
STDCXX-109
* etc/config/makefile.rules ($(CATFILE
Farid Zaripov wrote:
-Original Message-
From: Andrew Black [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 16, 2007 5:45 PM
To: stdcxx-dev@incubator.apache.org
Subject: Re: __rw_once warnings in non-reentrant Windows builds?
I'm not certain this is relevant, but MSVC 8.0 doesn't
[
https://issues.apache.org/jira/browse/STDCXX-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535295
]
Martin Sebor commented on STDCXX-262:
-
Looks like the patch committed at rev 583667
(http://svn.apache.org
[
https://issues.apache.org/jira/browse/STDCXX-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535304
]
Martin Sebor commented on STDCXX-600:
-
While switching the order the std::exception virtual members either way
[
https://issues.apache.org/jira/browse/STDCXX-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535305
]
Martin Sebor commented on STDCXX-600:
-
Part of the problem is that we're defining classes that are defined
Farid Zaripov wrote:
-Original Message-
From: Martin Sebor [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 16, 2007 5:52 PM
To: stdcxx-dev@incubator.apache.org
Subject: Re: 4.2.0-rc-6, final candidate
Out of curiosity, how do you test this? (I tested by building
4.1.3 examples
The 4.2.0 README is ready for review. Corrections, comments,
or suggestions for improvements are welcome.
Thanks
Martin
Martin Sebor wrote:
The 4.2.0 README is ready for review. Corrections, comments,
or suggestions for improvements are welcome.
Hit the Send button too soon... A link to the README might be helpful:
http://svn.apache.org/repos/asf/incubator/stdcxx/branches/4.2.0/README
Thanks
Martin
[
https://issues.apache.org/jira/browse/STDCXX-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor updated STDCXX-391:
Severity: Cosmetic
Fix Version/s: (was: 4.2)
4.2.1
Since the Look
Andrew Black wrote:
Martin Sebor wrote:
Andrew Black wrote:
Martin Sebor wrote:
[snip]
CRT's, so the 11s builds are compiled with the same options as the 15s
(11d == 15d, 8s|d == 12s|d).
Ugh. That means we've been doing a whole bunch of redundant builds
on Windows.
I think it would be more
Travis Vitek wrote:
I came up with three solutions to STDCXX-509. I don't really like any of
them, but here goes.
Thanks for taking the time to work on this!
1. Conditionally compile the change so that it is enabled for
platforms
with _RWSTD_NO_OBJECT_MANGLING defined, leaving the
/viewvc?rev=583655view=rev
Log:
2007-10-10 Martin Sebor [EMAIL PROTECTED]
* 21.string.io.stdcxx-206.cpp: Regression test for STDCXX-206.
Added:
incubator/stdcxx/trunk/tests/regress/21.string.io.stdcxx-206.cp
p (with props)
Added: incubator/stdcxx/trunk/tests/regress/21
-To: stdcxx-dev@incubator.apache.org
To: [EMAIL PROTECTED]
Author: sebor
Date: Mon Oct 15 12:58:38 2007
New Revision: 584880
URL: http://svn.apache.org/viewvc?rev=584880view=rev
Log:
2007-10-15 Martin Sebor [EMAIL PROTECTED]
* NO_OBJECT_MANGLING.cpp: New config test to determine whether
[
https://issues.apache.org/jira/browse/STDCXX-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534963
]
Martin Sebor commented on STDCXX-552:
-
I've just merged the latest trunk/doc to branches/4.2.0/doc:
http
Travis Vitek wrote:
No. I should probably double-check before opening my yapper. Here is the
the log from the windows configuration step. Both source files are
compiled and the final link line links both objects as you're expecting.
Great, thanks for the confirmation! I've configured the
Just as a heads up, even though this is a rather short notice,
since this test works as expected even on Windows/MSVC I'll go
ahead and merge it to 4.2.0 in preparation for the STDCXX-509
fix. If anyone has a problem with this, speak up.
Martin
Martin Sebor wrote:
Travis Vitek wrote:
No. I
[
https://issues.apache.org/jira/browse/STDCXX-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor updated STDCXX-553:
Affects Version/s: trunk
Fix Version/s: 4.2
[EDG eccp/gcc 4] errors on float.h macros
[
https://issues.apache.org/jira/browse/STDCXX-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor closed STDCXX-553.
---
Resolution: Fixed
Resolved by fixing STDCXX-394. Closing.
[EDG eccp/gcc 4] errors on float.h
[
https://issues.apache.org/jira/browse/STDCXX-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor reassigned STDCXX-553:
---
Assignee: Martin Sebor
[EDG eccp/gcc 4] errors on float.h macros
[
https://issues.apache.org/jira/browse/STDCXX-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor updated STDCXX-553:
Affects Version/s: (was: trunk)
Fix Version/s: (was: 4.2)
Whoops
[
https://issues.apache.org/jira/browse/STDCXX-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor closed STDCXX-591.
---
Resolution: Duplicate
Closed as a duplicate of STDCXX-414.
[EDG eccp/Linux] error #70
Components: Build
Affects Versions: trunk
Environment: EDG eccp 3.9 on Solaris 9
Reporter: Martin Sebor
Assignee: Martin Sebor
The top of 4.2.0 fails to build with EDG eccp 3.9 on Solaris 9 with the error
below:
$ nice gmake BUILDTYPE=11s BUILDDIR=/build/sebor
[
https://issues.apache.org/jira/browse/STDCXX-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor closed STDCXX-599.
---
Resolution: Fixed
Fix Version/s: 4.2
Fix confirmed in a manual build. Closing.
[EDG eccp
[
https://issues.apache.org/jira/browse/STDCXX-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor closed STDCXX-598.
---
Resolution: Fixed
Fix Version/s: 4.2
This is fixed in 4.2, possibly by the patch for STDCXX
[
https://issues.apache.org/jira/browse/STDCXX-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor updated STDCXX-336:
Fix Version/s: (was: 4.2)
4.2.1
Due to the lack of time this is not going
I'm afraid I'm not quite done with all my issues, most notably
with STDCXX-509 (although I have committed a partial solution,
I still need to cook something up for MSVC). I'm hoping to get
things wrapped up and have the candidate by the end of tomorrow.
Martin
Martin Sebor wrote:
After
[
https://issues.apache.org/jira/browse/STDCXX-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor resolved STDCXX-552.
-
Resolution: Fixed
Thanks, Travis. I think we can consider the issue fully resolved. Closing
[
https://issues.apache.org/jira/browse/STDCXX-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535048
]
Martin Sebor commented on STDCXX-509:
-
The change committed at rev 584981
(http://svn.apache.org/viewcvs?view
After I generated/updated the latest ChangeLogs I noticed that we have
been less than completely consistent in how we refer to changed files
in Change Log entries. Most of the time, although not all of the time,
we just mention the file name w/o the directory prefix. That's not a
big deal when
[
https://issues.apache.org/jira/browse/STDCXX-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534658
]
Martin Sebor commented on STDCXX-552:
-
Travis, could you please attach the output of RAT on the latest release
Issue Type: Bug
Components: Build
Affects Versions: trunk
Environment: EDG eccp 3.10 with gcc 4.1.1-52.el5 on Red Hat Enterprise
Linux Server release 5 (Tikanga)
Reporter: Martin Sebor
Fix For: 4.2.1
The library fails to compile with the EDG
[
https://issues.apache.org/jira/browse/STDCXX-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor closed STDCXX-589.
---
Resolution: Fixed
Nightly build results confirm the problem has been resolved. Closing.
[EDG eccp
[
https://issues.apache.org/jira/browse/STDCXX-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor closed STDCXX-588.
---
Resolution: Fixed
After the changes the error no longer appears in nightly build results. Closing
[
https://issues.apache.org/jira/browse/STDCXX-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor closed STDCXX-590.
---
Resolution: Fixed
Nightly build logs confirm that the change has fixed the problem: the majority
[
https://issues.apache.org/jira/browse/STDCXX-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor closed STDCXX-586.
---
Resolution: Fixed
Nightly build results confirm that this issue has been resolved. Closing.
[eccp
[
https://issues.apache.org/jira/browse/STDCXX-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor closed STDCXX-407.
---
Resolution: Fixed
Looks like we've got them all. The only ones remaining are the ones
[
https://issues.apache.org/jira/browse/STDCXX-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor closed STDCXX-278.
---
Resolution: Fixed
Fixed as follows:
http://svn.apache.org/viewvc?rev=584618view=rev
http
[
https://issues.apache.org/jira/browse/STDCXX-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor updated STDCXX-574:
Component/s: Documentation
Patch Info: [Patch Available]
Affects Version/s
[
https://issues.apache.org/jira/browse/STDCXX-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor reassigned STDCXX-574:
---
Assignee: Martin Sebor (was: Marc Betz)
Correct UG intro sections to eliminate Rogue Wave
[
https://issues.apache.org/jira/browse/STDCXX-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor closed STDCXX-574.
---
Resolution: Fixed
The buildspace fix was applied while checking in your patch for STDCXX-407
here
Farid Zaripov wrote:
Why -nostdinc++ compiler option is used when building the stdcxx on
gcc?
To prevent the native C++ headers from being accidentally included.
I know that this option prevents including the gcc C++ headers, but
the C++
headers are included on MSVC and nothing bad was
[
https://issues.apache.org/jira/browse/STDCXX-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534696
]
Martin Sebor commented on STDCXX-505:
-
See the thread below for a discussion of this page:
http://www.nabble.com
[
https://issues.apache.org/jira/browse/STDCXX-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534700
]
Martin Sebor commented on STDCXX-109:
-
The latest Darwin 8.10.1 (possibly via XCode 2.0?) comes with the gencat
[
https://issues.apache.org/jira/browse/STDCXX-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor updated STDCXX-224:
Severity: Incorrect Behavior
Affects Version/s: (was: 4.1.3
[
https://issues.apache.org/jira/browse/STDCXX-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor closed STDCXX-224.
---
Resolution: Cannot Reproduce
The problem cannot be reproduced with any Apache stdcxx release.
std
[
https://issues.apache.org/jira/browse/STDCXX-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor closed STDCXX-555.
---
Resolution: Invalid
The error was caused an incorrectly configured compiler. The EDG eccp demo
[
https://issues.apache.org/jira/browse/STDCXX-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor updated STDCXX-314:
Affects Version/s: (was: 4.1.3)
(was: 4.1.2)
I cannot reproduce
[
https://issues.apache.org/jira/browse/STDCXX-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor closed STDCXX-314.
---
Resolution: Cannot Reproduce
Cannot reproduce. I suspect I might have made some bad local changes
[
https://issues.apache.org/jira/browse/STDCXX-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534708
]
Martin Sebor commented on STDCXX-504:
-
I'm afraid I missed/forgot about an important detail: Rogue Wave owns
[
https://issues.apache.org/jira/browse/STDCXX-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor updated STDCXX-506:
Priority: Minor (was: Major)
Affects Version/s: 4.1.2
4.1.3
[
https://issues.apache.org/jira/browse/STDCXX-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor updated STDCXX-328:
Severity: Compiler Error
Fix Version/s: (was: 4.2)
4.2.1
After dispatching the remaining issues scheduled for 4.2.0(*) I'd
like to merge the few outstanding minor fixes and docs changes to
4.2.0 and create the (hopefully) final release candidate at the
end of the day (US/Mountain) tomorrow. If anyone has any concerns
please raise them ASAP.
[*] Here's
[
https://issues.apache.org/jira/browse/STDCXX-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor closed STDCXX-262.
---
Resolution: Fixed
Fix confirmed. Closing.
[gcc 4.0.1/Mac OS X 10.4.6 Tiger] multiple vtable
401 - 500 of 2631 matches
Mail list logo
