Re: Problems when compiling glib 2.4.0 with mingw

[Vincent Torri <torri math u-strasbg fr>]

On Wed, 24 Mar 2004, Tor Lillqvist wrote:

> Vincent Torri writes:
>  > *** Warning: This system can not link to static lib archive
>  > ./glib/libglib-2.0.la.
>  > *** 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.
>
> (Presumably that message said "../glib/libglib-2.0.la", not
> "./glib/..."?) Hmm. libtool problems certainly can be very confusing,
> and hard to debug. I notice that the libtool packaged with the glib
> 2.4.0 tarball is 1.5.2, while the one I use is 1.5, it's possible that
> there has been some odd change in it...

I have installed libtool 1.5.2. I get the same message.

> At what point did you get this message? 

gvaluetype is compiled (gvaluetype.o is generated), then
gobject-win32res.lo is build, then libtolls is invoked and there is the
warning message. Here is these 3 stages:

 gcc -mcpu=pentium3 -DHAVE_CONFIG_H
-I. -I. -I.. -DG_LOG_DOMAIN=\"GLib-GObject\" -I.. -I../glib
-I.. -DG_DISABLE_CAST_CHECKS -DG_DISABLE_DEPRECATED -DGOBJECT_COMPILATION
-DG_DISABLE_CONST_RETURNS -I/target/include -O3 -mms-bitfields -Wall -MT
gvaluetypes.lo -MD -MP -MF .deps/gvaluetypes.Tpo -c gvaluetypes.c
-DDLL_EXPORT -DPIC -o .libs/gvaluetypes.o
cd .. && /bin/sh ./config.status gobject/gobject.rc
config.status: creating gobject/gobject.rc
../build/win32/lt-compile-resource gobject.rc gobject-win32res.lo
Using zero as build number
/bin/sh ../libtool --mode=link gcc -mcpu=pentium3  -O3 -mms-bitfields
-Wall  -L/target/lib -o libgobject-2.0.la -rpath /target/lib -version-info
400:0:400 -export-dynamic -no-undefined -export-symbols ./gobject.def
gboxed.lo gclosure.lo genums.lo gobject.lo gparam.lo gparamspecs.lo
gsignal.lo gsourceclosure.lo gtype.lo gtypemodule.lo gtypeplugin.lo
gvalue.lo gvaluearray.lo gvaluetransform.lo gvaluetypes.lo
gobject-win32res.lo ../glib/libglib-2.0.la -lintl  

*** Warning: This system can not link to static lib archive
../glib/libglib-2.0.la.
*** 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.

right after that, there is of course lots "undefined referece... " when
trying to link libgobject-2.0.dll

> Had it built a static libglib, or a DLL? 

no dll has been built

> The intention is that only a DLL is built. What does the
> libglib-2.0.la you produced contain?

# libglib-2.0.la - a libtool library file
# Generated by ltmain.sh - GNU libtool 1.5.2 (1.1220.2.60 2004/01/25
12:25:08)
#
# Please DO NOT delete this file!
# It is necessary for linking the library.

# The name that we can dlopen(3).
dlname=''

# Names of this library.
library_names=''

# The name of the static archive.
old_library='libglib-2.0.a'

# Libraries that this one depends upon.
dependency_libs=' -L/target/lib -liconv -lwsock32 -lintl  '

# Version information for libglib-2.0.
current=400
age=400
revision=0

# Is this an already installed library?
installed=no

# 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='/target/lib'


I will be far from my computer for some days. don't expect any answer
before monday

thanks !

Vincent TORRI