[ODBC-127] MAriaDB Connector ODBC Build Failure Created: 2017-12-21  Updated: 2018-01-18  Resolved: 2018-01-18

Status: Closed
Project: MariaDB Connector/ODBC
Component/s: General
Affects Version/s: 3.0.2
Fix Version/s: 3.0.2

Type: Bug Priority: Major
Reporter: Chandranana Assignee: Lawrin Novitsky
Resolution: Won't Fix Votes: 0
Labels: None
Environment:

SLES 12 SP3 s390x


 Description   

We have been trying to build MariaDB connector-odbc from source. We have cloned from https://github.com/MariaDB/mariadb-connector-odbc/releases v 3.0.2.
Our OS is sles12-sp3 and arch is s390x.
We have managed to install mysql headers and libs and set the following ENV variables :
MYSQL_INCLUDE_DIR
MYSQL_LIB_DIR
MYSQL_DIR

When we do cmake ../mariadb-connector-odbc we get the following logs:
-- Found MariaDB includes: /home/test/server-mariadb-10.2.10/include
– MariaDB not found. Includes: /home/test/server-mariadb-10.2.10/include, Libs:
CMake Error at CMakeLists.txt:133 (MESSAGE):
MariaDB not found

– Configuring incomplete, errors occurred!
See also "/home/test/build/CMakeFiles/CMakeOutput.log".
See also "/home/test/build/CMakeFiles/CMakeError.log".
CMake Error: Unable to open check cache file for write. /home/test/build/CMakeFiles/cmake.check_cache

We need to know what is that we are missing to make the build pass.

 Comments   
Comment by Lawrin Novitsky [ 2018-01-10 ]

Sorry for the long delay with answer. But since I can see ODBC-128, and since s390x is too rare here, to suspect the reports to be from different source, may I assume that you have managed to build the connector?
But to answer your question - our cmake script look for MARIADB_ env variables. Also it's preferable to link against Connector/C, and not the library from server distribution. However headers/lib from 10.2 distribution may work.
Also due to ODBC-118, to build 3.0.2 one needs to build C/C from source from git repo, as the build won't work with latest C/C release

Comment by Lawrin Novitsky [ 2018-01-18 ]

I am closing this issue as I don't think there is a bug here, and there is nothing to fix

Generated at Thu Feb 08 03:26:25 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.