mdbtools compiled from source does not work where debian package does

Hi,

I have a problem with mdbtools on OSX 10.6 (installed via macports). I
have this JET3 database that seems to be parsed correctly on my ubuntu
box; but fails to be read correctly on OSX with the same version of
mdbtools.

For example, mdb-tables on OSX returns no tables:

    levin@rhea:~ $ uname -a
    Darwin rhea.local 10.3.0 Darwin Kernel Version 10.3.0: Fri Feb 26
11:58:09 PST 2010; root:xnu 1504.3.12~1/RELEASE_I386 i386
    levin@rhea:~ $ port list mdbtools
    mdbtools                       @0.6pre1        databases/mdbtools
    levin@rhea:~ $ md5 db.mdb
    MD5 (db.mdb) = c1be560bede6c55e53651f7c6e7ff2b8
    levin@rhea:~ $ mdb-ver -M db.mdb
    mdbtools v0.6pre1
    JET3
    levin@rhea:~ $ mdb-tables db.mdb

    levin@rhea:~ $

For comparison, here is the (correct) output from ubuntu:

    levin@q:~$ uname -a
    Linux q 2.6.24-26-generic #1 SMP Tue Dec 1 17:55:03 UTC 2009
x86_64 GNU/Linux
    levin@q:~$ aptitude show mdbtools | grep Version
    Version: 0.5.99.0.6pre1.0.20051109-4
    levin@q:~$ md5sum db.mdb
    c1be560bede6c55e53651f7c6e7ff2b8  db.mdb
    levin@q:~$ mdb-ver -M db.mdb
    mdbtools v0.6pre1
    JET3
    levin@q:~$ mdb-tables db.mdb
    BE BG EBM20R EBM20RA EBM20Z EBM87R EBM87Z EBM96R GOA88R GOA88Z
GOA96R GOA96RAS GOA96Z KAPITEL KEYS EBM20RAS EBM96Z GOA96RA KEYTABS
    levin@q:~$

Something is clearly wrong,

(Further testing shows that the current mdbtools from sourceforge
compiled from source on the ubuntu box also gives the incorrect
results. The problem therefore seems to be fixed by one of the patches
to the debian mdbtools package [1] but nothing jumps out)

Anyone have seen this kind of problem before or have an idea how to debug this?


Thank you,
Levin Alexander

[1] http://packages.debian.org/changelogs/pool/main/m/mdbtools/mdbtools_0.5.99.0.6pre1.0.20051109-6/changelog

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev