Just in case anyone with FC4 and maybe other distros were trying to use
unixODBC-2.2.11 and wine's built in odbc32. If your app errors out when
you issue a query with an undefined symbol of __post_internal_error you
will need to use an early snapshot of the 2.2.12 unixODBC that resolves
this issue...
Nick Gorham wrote:
Adam Gibson wrote:
Using freetds-0.63-1.2.fc4.rf from dag and the official
unixODBC-2.2.11-3.FC4.1 package from Fedora updates. I have wine
configured to use unixODBC. Connecting to the database works but when
the app issues a query wine fails with the error:
[user@host tmp]$ wine testdbapp.exe
/usr/bin/wine-pthread: symbol lookup error: /usr/lib/libodbccr.so.1:
undefined symbol: __post_internal_error
Sure enough ldd thinks it is undefined.
[user@host tmp]$ ldd -r /usr/lib/libodbccr.so.1.0.0
undefined symbol: dm_log_write (/usr/lib/libodbccr.so.1.0.0)
undefined symbol: __post_internal_error (/usr/lib/libodbccr.so.1.0.0)
libodbc.so.1.0.0 is not exporting it either.
[user@host tmp]$ nm -oD /usr/lib/libodbc.so.1.0.0|grep
post_internal_error
I am at a loss trying to figure out where to go from here. __info.c in
DriverManager has the function according to the source tarball for
unixODBC-2.2.11. The makefiles are a little over my head to figure
out though. Anyone know how I can force libodbc.so.1.0.0 to export
the __post_internal_error function?
Get the 2.2.12 snapshot,
ftp://ftp.easysoft.com/pub/unixODBC/unixODBC-2.2.12.tar.gz that should
fix this.
_______________________________________________
wine-users mailing list
wine-users@xxxxxxxxxx
http://www.winehq.org/mailman/listinfo/wine-users
