After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 651607 - './configure --host=i686-pc-mingw32 --with-mdb=no' still configures to use mdb
'./configure --host=i686-pc-mingw32 --with-mdb=no' still configures to use mdb
Status: RESOLVED FIXED
Product: libgda
Classification: Other
Component: general
4.2.x
Other Linux
: Normal normal
: ---
Assigned To: malerba
gnome-db Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-06-01 04:07 UTC by Ryan Laboucane
Modified: 2011-06-02 16:45 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ryan Laboucane 2011-06-01 04:07:51 UTC
Basically, MDB support is still configured in for any host-os that is on mingw32. Without mdbtools installed or with mdbtools-0.6.pre1 installed, the build subsequently fails. Other versions of mdbtools not tested.

This was attempted on an Ubuntu x64 Natty with both libgda-4.2.6 and libgda-4.2.7

running './configure --host=i686-pc-mingw32 --with-mdb=no' produces this output at the end:

<code>
...
 Configuration summary for version 4.2.7
   Installation prefix = /usr/local
   Building GTK+ UI extension: yes
   Building Libxslt extension: yes
   Building libgda GObject Introspection: no
   Building libgda-ui GObject Introspection: no
   Compiled providers:
      Berkeley DB = no
      Berkeley DB SQL = no
      MDB (MS Access) = yes (embedded)
      MySQL = no
      Oracle = no
      PostgreSQL = yes
      SQLite = yes (embedded)
      SQLCipher = yes
      JDBC = no
      WEB = no
</code>

Basically, MDB support is still configured when the host-os is mingw32. Naturally, since I don't have mdbtools installed, the build subsequently fails.

Specifying any other host seems to configure (the lack of) MDB support properly.

Configuring with other architectures not tested (by me).
Comment 1 Ryan Laboucane 2011-06-01 08:58:54 UTC
Changed importance level to normal, as I've found a workaround for mingw32 (and possibly 64?) hosts:

The workaround involves editing the 'libgda_source_dir/providers/Makefile' after running './configure --host=i686-pc-mingw32 --with-mdb=no'

Commenting out the line that reads:

GDA_MDB_SERVER = mdb

so that it reads:

#GDA_MDB_SERVER = mdb

This allows a normal build.
Comment 2 malerba 2011-06-01 13:43:57 UTC
I've just committed a patch which honors the --with-mdb option for Window, it should fiw you problem, see http://git.gnome.org/browse/libgda/commit/?h=LIBGDA_4.2&id=9f7f8351a64d629ac70e8896d84566ae278e0cc2

However I don't understand why the MDB provider did not compile as it was supposed to use the embedded version (i.e. the part of MDBTools required are inserted into Libgda's sources), as the summary after ./configure run says ("MDB (MS Access) = yes (embedded)"). Could you send me the result of the make output in your configuration?
Comment 3 Ryan Laboucane 2011-06-02 04:56:21 UTC
This solves my problem, as the library now builds, however testing reveals that now it does not honor --with-mdb=yes.

I have sent you my logfile directly prior to this posting.
Comment 4 malerba 2011-06-02 16:45:35 UTC
The distribution did not include MDBTool's includes, this is now fixed, see http://git.gnome.org/browse/libgda/commit/?id=4d84a6f3013a4cc66f642a55356f0df72a26a31c