On Oct 31, 2012, at 6:50 AM, Derek Atkins <warl...@mit.edu> wrote:
> John Ralls <jra...@ceridwen.us> writes:
>
>>>> So in order to make sure there wasn't something bad in my build
>>>> tree, I made new 'gnucash-clean' and 'gnucash-clean-build'
>>>> directories, checked-out a fresh set of sources and rebuilt
>>>> it. "make" worked, but I got the same result with "make check". Does
>>>> 'Error 143' mean anything to you?
>>>
>>> I'm also building out of tree. I remember I had to make a softlink to
>>> the xml test file from the source directory to the build directory
>>> before the tests worked. This may have to be corrected in the build
>>> scripts.
>>
>> Ah, that's the likely culprit. There's an XML file that's loaded by
>> the XML backend, and the test will program will crash if it can't find
>> the file. Before my last round of changes the test program didn't even
>> try to load because the xml backend wasn't loaded. There weren't any
>> asserts to check that it had, so it would always pass without actually
>> testing anything. Odd, though, that you're getting that weird error
>> message instead of the assert message from checking for backend errors
>> right after trying to load the file.
>
> Perhaps change the test to use ${srcdir}/...
A little more involved than that, because the test file name was #defined
inside the C files, but now fixed in r22511.
Regards,
John Ralls
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
