Re: Xerces-C 3.1.2 beta-2 available, call for testing

2015-03-06 Thread Cantor, Scott
In case it matters, this is what I'm using with configure: configure: Report: configure: File Manager: POSIX configure: Mutex Manager: POSIX configure: Transcoder: icu configure: NetAccessor: socket configure: Message Loader: inmemory Any of those different in your build that's giving

Re: Xerces-C 3.1.2 beta-2 available, call for testing

2015-03-06 Thread Gareth Reakes
On 6 Mar 2015, at 14:22, Cantor, Scott canto...@osu.edu wrote: On 3/6/15, 4:17 AM, Gareth Reakes gar...@reakes.com wrote: On OSX compiles fine but test run produces this attached failure diff. Compared to 3.1.1 you mean? No, compared to the committed test output file -

Re: Xerces-C 3.1.2 beta-2 available, call for testing

2015-03-06 Thread Cantor, Scott
On 3/6/15, 9:34 AM, Gareth Reakes gar...@reakes.com wrote: On OSX compiles fine but test run produces this attached failure diff. Somewhat surprisingly, on my OS X laptop, my test run has identical output to what's checked in, no diff. But I did that out of subversion, not the tarball, so I'll

Re: Xerces-C 3.1.2 beta-2 available, call for testing

2015-03-06 Thread Cantor, Scott
On 3/6/15, 4:17 AM, Gareth Reakes gar...@reakes.com wrote: On OSX compiles fine but test run produces this attached failure diff. Compared to 3.1.1 you mean? How do the tests get run as a unit? Do you know which test is giving that different result? -- Scott

Re: Xerces-C 3.1.2 beta-2 available, call for testing

2015-03-06 Thread Cantor, Scott
On 3/6/15, 9:34 AM, Gareth Reakes gar...@reakes.com wrote: No, compared to the committed test output file - scripts/sanityTest_ExpectedResult.log Ok, I'll look at when that was committed. make check So it runs them as part of the test build? Ok, I didn't notice that, will review that. --

Re: Xerces-C 3.1.2 beta-2 available, call for testing

2015-03-06 Thread Cantor, Scott
On 3/6/15, 10:08 AM, Gareth Reakes gar...@reakes.com wrote: Do you have the file in your checkout? /xerces-c-3.1.2/samples/data/long.xml No, it's not in the dist target, so that's the problem. I'll add it and republish a third beta today. One of the things I'm trying to clean up is the dist.

Re: Xerces-C 3.1.2 beta-2 available, call for testing

2015-03-06 Thread Gareth Reakes
On 6 Mar 2015, at 15:00, Cantor, Scott canto...@osu.edu wrote: On 3/6/15, 9:34 AM, Gareth Reakes gar...@reakes.com wrote: On OSX compiles fine but test run produces this attached failure diff. Somewhat surprisingly, on my OS X laptop, my test run has identical output to what's checked

Re: Xerces-C 3.1.2 beta-2 available, call for testing

2015-03-06 Thread Gareth Reakes
On 6 Mar 2015, at 15:04, Cantor, Scott canto...@osu.edu wrote: In case it matters, this is what I'm using with configure: configure: Report: configure: File Manager: POSIX configure: Mutex Manager: POSIX configure: Transcoder: icu configure: NetAccessor: socket configure:

Re: Xerces-C 3.1.2 beta-2 available, call for testing

2015-03-06 Thread Gareth Reakes
On OSX compiles fine but test run produces this attached failure diff. G diff Description: Binary data On 6 Mar 2015, at 02:38, Cantor, Scott canto...@osu.edu wrote: I've uploaded a second beta of Xerces-C 3.1.2 [2] containing a couple of small fixes (VS2012 solution file fix, a

Xerces-C 3.1.2 beta-2 available, call for testing

2015-03-05 Thread Cantor, Scott
I've uploaded a second beta of Xerces-C 3.1.2 [2] containing a couple of small fixes (VS2012 solution file fix, a backport of an XMLString binToText bug reported yesterday) and a tweak to the automake settings so I can generate a ZIP distribution from make dist. Just want to keep the test