[redland-dev] Raptor 1.4.3 Test FAILs

[Dave Beckett]

On Mon, 3 Jan 2005 18:18:45 -0500
Christopher Schmidt <crschmidt at crschmidt.net> wrote:

> Several of the tests in the latest Raptor FAIL under my system, when 
> running make check .
> 
> Per the request of the output of make check, I've attached the test 
> output (STDOUT + STDERR).
>
> The tests that fail are:
> FAIL: raptor_rfc2396_test 
> lt-raptor_rfc2396_test: raptor_uri_resolve_uri_reference(foo:, 
> not_scheme:blah) FAILED giving 'foo:' != 'foo:/not_scheme:blah'
> 
> FAIL: raptor_sequence_test 
> /home/crschmidt/projects/rd-.9.19/redland-0.9.19/raptor-1.4.3/.libs/l
> t-raptor_sequence_test: symbol lookup error: 
> /home/crschmidt/projects/rd-.9.19/redland-0.9.19/raptor-1.4.3/.libs/l
> t-raptor_sequence_test: undefined symbol: raptor_sequence_join

We've been here before I think.  You are linking the
raptor_sequence_test against an older version of the library which
doesn't have the raptor_sequence_join that's new in 1.4.3. It looks
like it must be one from redland-0.9.19.  Not surprisingly, it fails.

This is the cause of the other two failures above and below.

> 
> FAIL: raptor_xml_writer_test
> /bin/sh: line 1: 12666 Segmentation fault      ${dir}$tst
> 
> The second failure seems like it's probably a local issue of mine. The
> 
> xml_writer test is probably most significant given that it's a new 
> feature. The backtrace is:
> 
> #0  0x08053a30 in ?? ()
> #1  0x400231fc in raptor_namespaces_init (nstack=0x8053288, 
>     uri_handler=0x80539b0, uri_context=0x40039d60, 
>     error_handler=0x4003569c <__func__.1+1116>, error_data=0x4003569c,
>     
>     defaults=0) at raptor_namespace.c:128
> #2  0x4002ca5d in raptor_new_xml_writer (uri_handler=0x80539b0, 
>     uri_context=0x40039d60, error_handler=0, error_data=0x8053968, 
>     canonicalize=0) at raptor_xml_writer.c:101
> #3  0x08048f53 in main (argc=1, argv=0x4003569c) at 
> raptor_xml_writer.c:312
> 
> If there's anything I can do to be more specific or more helpful,
> please let me know. Note that I've never run make check before, so
> this may not be something new, just something I've not encountered.

Try 'make uninstall' before starting building to clean out any older
system installed libraptor.  Then run configure again.

OR, do a 'make install' and then do a 'make check' to ensure that the
test programs are linking against 1.4.3 libraries.

Dave