Bug #71158 | mysql-odbc5.2.6 compiled fail against unixODBC-2.2.11 and mysql5.6.14 on suse11 | ||
---|---|---|---|
Submitted: | 17 Dec 2013 2:56 | Modified: | 18 Jan 2014 6:38 |
Reporter: | john john | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
Version: | mysql-connector-odbc-5.2.6 | OS: | Linux (suse linux 11) |
Assigned to: | Bogdan Degtyariov | CPU Architecture: | Any |
Tags: | ODBC |
[17 Dec 2013 2:56]
john john
[18 Dec 2013 6:38]
Bogdan Degtyariov
Hi John, I am afraid you did not interpret our documentation correctly because your compile string has parameters that cause the build failure: -DMYSQL_LINK_FLAGS=mysql wrong use of the option that causes the error "gcc: mysql: No such file or directory" There is no such link flag as "mysql". This particular option was introduced to let the user override the link flags returned by mysql_config script if necessary (in most of cases it is not). So, just remove this option from the command line -DMYSQL_CXXFLAGS=mysql is same as the option above, but it is for the C++ compiler flags. Remove it from the command line. -DMYSQLCLIENT_LIB_NAME=mysqlclient is not right as well. The documentation says to specify the full file name, which is either libmysqlclient.so (for dynamic linking with mysqlclient library, set by default) or libmysqlclient.a (for static linking, to make your driver shared library independent from libmysqlclient.so). If you want the dynamic linking it can be removed from the command line. Please check the documentation, which shows what each option does: http://dev.mysql.com/doc/refman/5.6/en/connector-odbc-installation-source-unix.html That is all for cmake options. However, you should keep in mind that UnixODBC 2.2.11 might have problems in 64-bit mode because of SQL type mapping. We recommend using UnixODBC 2.2.14.
[19 Jan 2014 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".