RE: please update libXML (undefined references)

["Robert Collins" <robert dot collins at syncretize dot net>]

> -----Original Message-----
> From: Gerrit P. Haase [mailto:gp@familiehaase.de] 
> Sent: Monday, 22 July 2002 3:35 PM


> >> I wonder why I didn't see all this weird problems when
> >> building the previous version?
> 
> That was the same point, I did the build inside the sourcedir and
> installed it directly in my real system.
> 
> Now I see:
> (cd /sourcecode/XML/new/libxml2-2.4.23/python; sh ../libtool \
> --mode=relink i686-pc-cygwin-gcc -O2 -o libxml2mod.la -rpath \
> /usr/lib/python2.2/site-packages -module -avoid-version -L../.libs \
> libxml.lo types.lo libxml2-py.lo ../libxml2.la \
> -L/usr/lib/python2.2/config -lpython2.2)
> ---------------------------- This is still correct...
> 
> libtool: link: warning: `/lib/libiconv.la' seems to be moved
> i686-pc-cygwin-gcc -shared  .libs/libxml.o .libs/types.o \
> .libs/libxml2-py.o  -L/lib \
> --------------------^^^^^^^Wrong flag 1!!!
> -L/sourcecode/XML/new/libxml2-2.4.23/.libs -L/usr/lib -lxml2 \
> -------------------------------------------^^^^^^^^^Wrong flag 2!!!
> -L/usr/lib/python2.2/config -lpython2.2  -o .libs/cygxml2mod.dll \
> -Wl,--image-base=0x10000000 -Wl,--out-implib,.libs/libxml2mod.dll.a
> 
> 
> Where do the flags come from?  Robert, is there a verbose or debug
> option for libtool?

Set -x might help. That's about all though.

As for the -lxml2 that you see there, this is a known shortcoming of
libtool. It's *by design*. The theory is that because some O/S must link
to the final location of the library, when linking on install, you must
link to the final location. This plays havoc with packaging programs
(rpm/dpkg etc) and the libxml2... Sh script is doing the same thing.

Rob