Re: mingw32 cross-compile: sys_lib_search_path setting insuffient

[Sebastien Sable]

Hi,

Guido Draheim <address@hidden> writes:

> The dll of my project does need some function from a
> a lib installed with the gcc - the libtool has support
> for this scheme as it uses "$CC --print-search-dirs",
> then greps it for the "libraries:" line, and puts it
> into sys_lib_search_path.
...
> So far, so good - but there is a bug.

Could this be the reason of this problem ? :

address@hidden:~/tim/dev/test$ /bin/sh ./libtool --mode=link c++ -g -O2 \
-o libblind.la -rpath /usr/local/cross-tools/i386-mingw32msvc/lib \
-no-undefined --noinhibit-exec -mconsole --export-all-symbols \
csdemo.lo audioenv.lo avenvironment.lo object.lo -lbraille
rm -fr .libs/libblind.la .libs/libblind.* .libs/libblind.*

*** Warning: This library needs some functionality provided by -lbraille.
*** I have the capability to make that library automatically link in when
*** you link to this library.  But I can only do this if you have a
*** shared version of the library, which you do not appear to have.
*** The inter-library dependencies that have been dropped here will be
*** automatically added whenever a program is linked with this library
*** or is declared to -dlopen it.

*** Since this library must not contain undefined symbols,
*** because either the platform does not support them or
*** it was explicitly requested with -no-undefined,
*** libtool will only create a static version of it.
ar cru .libs/libblind.a  csdemo.o audioenv.o avenvironment.o object.o 
i386-mingw32msvc-ranlib .libs/libblind.a
creating libblind.la
(cd .libs && rm -f libblind.la && ln -s ../libblind.la libblind.la)

Where the shared library _does_ indeed exist (and was created with
libtool) :

address@hidden:~/tim/dev/test$ ls 
/usr/local/cross-tools/i386-mingw32msvc/lib/libbraille*
/usr/local/cross-tools/i386-mingw32msvc/lib/libbraille-0.dll
/usr/local/cross-tools/i386-mingw32msvc/lib/libbraille.a
/usr/local/cross-tools/i386-mingw32msvc/lib/libbraille.la

And if not what can I do to have a more explicit message or at least a
log of what libtool is trying to do?

Thanks

-- 
Sébastien Sablé <address@hidden>
http://inova.snv.jussieu.fr/~sable/