On Thu, Dec 18, 2008 at 11:21:54AM +0100, Fridrich Strba wrote: > Yes, the gnu libiconv for instance will leave in the *.la file the > directory in which the library will be installed and that will create a > problem because libtool will not find it there.
I'm still not sure I understand. The libiconv.la file looks OK to me (see below). And we routinely link against libiconv. Rich. # libiconv.la - a libtool library file # Generated by ltmain.sh - GNU libtool 1.5.24 (1.1220.2.455 2007/06/24 02:13:29) # # Please DO NOT delete this file! # It is necessary for linking the library. # The name that we can dlopen(3). dlname='../bin/libiconv-2.dll' # Names of this library. library_names='libiconv.dll.a' # The name of the static archive. old_library='' # Libraries that this one depends upon. dependency_libs='' # Version information for libiconv. current=6 age=4 revision=0 # Is this an already installed library? installed=yes # Should we warn about portability when linking against -modules? shouldnotlink=no # Files to dlopen/dlpreopen dlopen='' dlpreopen='' # Directory that this library needs to be installed in: libdir='/usr/i686-pc-mingw32/sys-root/mingw/lib' -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into Xen guests. http://et.redhat.com/~rjones/virt-p2v _______________________________________________ fedora-mingw mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/fedora-mingw
