Re: GSXML - read unknown type error and include problems

[Richard Frith-Macdonald]

On Thursday, May 23, 2002, at 09:22 AM, e.sammer wrote:

> There seems to be a problem with GS base and the libxml test as well as
> the GSXML classes. Basically, when running configure with the proper
> options the libxml test fails with the following:
>
> -- except from config.log --
>
> configure:11501: gcc -o conftest -g -O2 -I/usr/local/include/libxml2
> -fgnu-runtime -I/opt/gnustep/System/He
> aders  -L/opt/gnustep/System/Libraries/gnu-gnu-gnu
> -L/opt/gnustep/System/Libraries conftest.c -L/usr/local/l
> ib -lxml2 -lz -lpthread -lm  -lz -lcallback -lavcall >&5
> configure:11428:24: xmlversion.h: No such file or directory
> configure:11429:20: parser.h: No such file or directory
>
> Here's some system info:
>
> GNUstep: from cvs
> libxml2: 2.4.21 (from source)
> gcc: 3.1 (from source)
> xml2-config --cflags out: -I/usr/local/include/libxml2
> xml2-config --libs out: -L/usr/local/lib -lxml2 -lz -lpthread -lm
> SuSE 7.2

This appears to be a bug/feature of the version of libxml that you are 
using.
On other versions 'xml2-config --cflags' produces
'-I/usr/local/include/libxml2 -I/usr/local/include/libxml2/libxml'

> It seems that the test includes do not include the libxml directory
> which is causing the problem. This should definately be '#include
> <libxml/headerfile.h>' because with libxml version 1 has a compat
> symlink'd directory and libxml2 uses the libxml directory inside of
> $prefix/libxml2.

The code in the configure script which includes the libxml headers is
produced by libxml's own autoconf macro.  ie it's the way that libxml
says autoconf should test for the presence of libxml!

Obviously, your version is wrong, or the authors of libxml have
deliberately changed things in a way that's incompatible with older
versions!

If this is a deliberate change rather than a bug, we should probably
regenerate the configure script using a newer version of libxml (though
the version I'm using is already the latest debian testing package).
Does the source code you have include a change long which says that
this is a deliberate change?


As for the problems in GSXML themselves ... they should be fixed in CVS 
now.