On Mon, 2002-04-29 at 19:10, Stipe Tolj wrote: > Bruno David Simões Rodrigues wrote: > > > > xml2-config --cflags in some architectures (mandrake, probably redhat > > and suse) is returning only: > > > > -I/usr/include/libxml2 > > > > In debian, I have in changelogs: > > > > libxml2 (2.4.19-2) unstable; urgency=low > > > > * (...) > > * xml2-config --cflags will return same paths as previous versions > > (closes: #142229) > > > > And xml2-config returns correctly: > > -I/usr/include/libxml2/libxml -I/usr/include/libxml2 > > > > Shouldn't we be aware of that in configure and detect > > if it needs to add libxml ? > > Hmm, I don't think we should deal with bugs inside depending > packages?!
I've been read the changelog for libxml2 for debian and it looks that the right way to do it is to include "libxml/file.h". debian have patched xml2-config to maintain compatibility to last patch. (I mean, they've once patched to be like that, and now they "have" to have xml2-config to behave like that) But please everybody test it and say if it's still buggy. (I know that it fixes redhat and mandrake, debian is ok any way) > > Stipe > > [EMAIL PROTECTED] > ------------------------------------------------------------------- > Wapme Systems AG > > Münsterstr. 248 > 40470 Düsseldorf > > Tel: +49-211-74845-0 > Fax: +49-211-74845-299 > > E-Mail: [EMAIL PROTECTED] > Internet: http://www.wapme-systems.de > ------------------------------------------------------------------- > wapme.net - wherever you are
