On Sun, Oct 03, 2010 at 08:38:18PM +0200, Xypron wrote: > When I compile Connector/ODBC 5.1.7 from dev.mysql.com it creates > /usr/local/lib/libmyodbc5-5.1.7.so.
> I used > ./configure --enable-gui=no > This library works perfectly with iODBC. Did you rebuild this new version of myodbc using libiodbc2-dev, or unixodbc-dev? If you used libiodbc2-dev, what happens if you rebuild the current myodbc using libiodbc2-dev instead of unixodbc-dev? Is the original error reproducible with any programs built against unixodbc instead of iodbc? For instance, if you rebuild the glpk package against unixodbc, is the error still present? If you rebuild the pristine myodbc package against current unixodbc, is the issue present then? (myodbc was last built against the previous upstream version of unixodbc, 2.2.11.) Note that the upstream version of iodbc included in Debian is three years old, and is orphaned as of a year ago. I'm not sure why glpk is building against iodbc instead of unixodbc; we should really drop iodbc in favor of unixodbc, instead of carrying two implementations of the same library that can only result in gratuitous incompatibilites. > I wonder why the sizes of the library supplied by package libmyodbc > is so different: > /usr/local/lib/libmyodbc5-5.1.7.so 983612 bytes > /usr/lib/odbc/libmyodbc.so 293400 bytes Probably because your rebuild installs an unstripped binary instead of a stripped binary as required by policy. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
