Hallo David,
Am Montag, 22. Juli 2002 um 01:16 schriebst du:
> I believe I had a similar problem with libwmf.
> libwmf makes two libraries - lets call them A and B. libA
> is depends on libB. When libtool relinked libA during
> "make install" it linked libA with the installed version of
> libB, and not the libB I had just built. The older version
> of libB did not have some of the symbols in the new version
> and so it failed with "undefined reference" messages.
> The work around was to manually copy the new version of
> libB.dll.a into /usr/lib before retrying "make install".
> I don't know why libtool is relinking, as I don't think
> it is required and it does doesn't work in this case.
Yes, I verified this. I installed into the real filesystem instead of
the .instdir and then relinking works well.
>> 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?
Gerrit
--
"All faults& bugs are mine - Robert"
from squid/acinclude.m4, Sun Apr 21 05:21:21 2002
