The fix went in after 2.5. You'll have to pull from CVS or wait for 2.6 to get the fix. 2.6 is in the works, but I don't know when it will be released. (It's worth noting that you can often get a more stable system by pulling select bits from CVS. Xerces-C doesn't often do bug-fix releases.)
Xerces-C switched from bugzilla to Jira fairly recently, hence the confusion. Jira is authoritative. > -----Original Message----- > From: David Kramer [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 21, 2004 10:23 AM > To: xerces-c-dev > Subject: Issue XERCESC-1235 (errors compiling with GCC) > > Hi. I just joined this list today (though I did search the archives > first), because I just got an assignment at work to get > xerces working > with our system. > > We have an application that runs on AIX 5.2. We've been > using the xlC > compiler, but I'm now trying to port everything over to the > gcc compiler > (still using the native ld, as I can't get binutils working correctly > yet). We have xerces C++ 2.4, but we're willing to upgrade. > > I'm getting the same errors mentioned in that bug report, a la > http://www.mail-archive.com/[EMAIL PROTECTED]/msg13143.html > even though I'm using 2.4, and he's using 2.5. > > According to > http://nagoya.apache.org/jira/browse/XERCESC-1235?page=history > this problem is fixed, but I'm a little confused how to get the fix. > > If I download the most recent release, 2.5, will the fix be > in there? > > Or do I have to download from CVS? > > If that's the case, how long would I have to wait until the > next release > (my boss is rather conservative, and probably wouldn't go along with > grabbing a non-release)? > > Now, about the bug system. I see references to a Bugzilla > page for this > project (like on the release notes page), and to the Jira bug system > mentioned above. The bug numbers don't correlate. Which is > the right > one for xerces C++? What am I missing? > > Thanks in advance. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
