Re: [gnome-db] cygwin update - glib
- From: Rodrigo Moya <rodrigo gnome-db org>
- To: Margus Väli <mvali hot ee>
- Cc: GDA <gnome-db-list gnome org>
- Subject: Re: [gnome-db] cygwin update - glib
- Date: 03 Sep 2002 10:31:11 +0200
On Mon, 2002-09-02 at 16:01, Margus Väli wrote:
> Rodrigo Moya wrote:
> >>>>
> >>>>Bug reported on http://bugzilla.gnome.org/show_bug.cgi?id=92060
> >>>
> >>Yes, g_module_open()s .dll files just fine. I have no problems with
> >>postgres provider having hacked libgda/gda-config.c to include
> >>my cygwin windows path and .dll extension.
> >>
> >>But yes, glib has under cygwin serious problems with linking (against
> >>user32, kernel and other cygwin libraries that only provide a static
> >>.a library).
> >>
> ..
> > So, now let's see your linking problems. What are the exact errors?
>
> This is probably about some gcc command line parameter (CFLAGS).
> Find the output attached.
> CWD: in /usr/src/glib-2.0.6/gobject
> The symbols not found are indeed present in
> ../glib/.libs/libglib-2.0.a, but only with a '_' prefix.
> Linker complains about missing g_log, but we actually have _g_log
> for example -- the '_' prefix is already present in .lo files
> (like _g_log in ../glib/gmessages.lo)
>
hmm, as for the log, the problem is when linking libgobject, so it seems
you'll need to add $(top_builddir)/glib/libglib-2.0.la (or whatever path
it is) to the gobject/Makefile.am, so that it gets linked with
libglib-2.0. In linux this works because the library dependencies are
resolved when linking an application against the library, not when
linking a library against the library, which is what is happening here,
it seems. Try adding that, and tell us what you get.
About the user32.dll problem, I don't know :-(
cheers
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]