Re: [gnome-db] Compiling libgda on win32 with MinGW/MSYS

["Vivien Malerba" <vmalerba gmail com>]

On 4/3/07, Brecht Sanders <brecht sanders org> wrote:
> > > You can also use the programs in the "tools" directory:
> > > * gda-diagnose will produce HTML about a lot of things (this is
> > > probably the first one you want to try)
> >
> > Here I get an error popup: "Gda-ERROR **: Error opening directory
> > '......../lib/libgda-3.0/providers': No such file or directory
> > aborting..."
> > This is probably because I install to a temporary location before
> > packaging the Windows version, and then install it to the final
> > location.
> > I do this because on Windows you can't assume the exact absolute
> > location at compile time.
> > Is there any way to tell libgda where to look for its providers?
>   For now and for testing purposes I put the files in the expected path and
> I get the output below.
> What database does gda-diagnose use, or does it need additional parameters?
> Is the memory warning indicating a serious problem?
>
> $ ./gda-diagnose-3.0
> Output dir './GDA_DIAGNOSE_OUTPUT' exists and is writable
>
> ***MEMORY-WARNING***: gda-diagnose-3.0.exe[484]: GSlice: g_thread_init()
> must be called before all other GLib functions; memory corruption due to
> late invocation of g_thread_init() has been detected; this program is likely
> to crash, leak or unexpectedly abort soon...
>
> ** (gda-diagnose:484): CRITICAL **:
> gda_odbc_provider_get_server_version: assertion
> `GDA_IS_CONNECTION (cnc)' failed
>
> ** (gda-diagnose:484): CRITICAL **: gda_odbc_provider_supports: assertion
> `GDA_IS_CONNECTION (cnc)' failed
>
> ** (gda-diagnose:484): CRITICAL **: gda_odbc_provider_supports: assertion
> `GDA_IS_CONNECTION (cnc)' failed
>
> ** (gda-diagnose:484): CRITICAL **: gda_odbc_provider_supports: assertion
> `GDA_IS_CONNECTION (cnc)' failed
>
> ** (gda-diagnose:484): CRITICAL **: gda_odbc_provider_supports: assertion
> `GDA_IS_CONNECTION (cnc)' failed
>
> ** (gda-diagnose:484): CRITICAL **: gda_odbc_provider_supports: assertion
> `GDA_IS_CONNECTION (cnc)' failed
>
> ** (gda-diagnose:484): CRITICAL **: gda_odbc_provider_supports: assertion
> `GDA_IS_CONNECTION (cnc)' failed
>
> ** (gda-diagnose:484): CRITICAL **: gda_odbc_provider_supports: assertion
> `GDA_IS_CONNECTION (cnc)' failed
>
> ** (gda-diagnose:484): CRITICAL **: gda_odbc_provider_supports: assertion
> `GDA_IS_CONNECTION (cnc)' failed
>
> ** (gda-diagnose:484): CRITICAL **: gda_odbc_provider_supports: assertion
> `GDA_IS_CONNECTION (cnc)' failed
>
> ** (gda-diagnose:484): CRITICAL **: gda_odbc_provider_supports: assertion
> `GDA_IS_CONNECTION (cnc)' failed
>
> ** (gda-diagnose:484): CRITICAL **: gda_odbc_provider_supports: assertion
> `GDA_IS_CONNECTION (cnc)' failed
>
> ** (gda-diagnose:484): CRITICAL **: gda_odbc_provider_supports: assertion
> `GDA_IS_CONNECTION (cnc)' failed
>
> ** (gda-diagnose:484): CRITICAL **: gda_odbc_provider_supports: assertion
> `GDA_IS_CONNECTION (cnc)' failed
>
> ** (gda-diagnose:484): CRITICAL **: gda_odbc_provider_supports: assertion
> `GDA_IS_CONNECTION (cnc)' failed

The warnings about the GDA_IS_CONNECTION (cnc) failing is normal (the
way the test is written). However the warning about
***MEMORY-WARNING*** is not normal, I don't get it myself. Does it
display the same warning with other tools?

The gda-diagnose tool tests all the compiled providers, but tries to
connect to a database only for the DSN you give it on the command line
(if none, then it does not try to connect to any database). Run it
with --help for some info. The DSN must already be defined, so you can
start with the Sales one defined by default (it's an SQLite DB, I hope
it's correctly defined under Windows).

Cheers,

Vivien

PS: I'll put a sample DB and my configure script on a web server
tonight as they are quite big.