Hello! You can link your own binary to libodbcinst, in which case the linking problem should go away. Can you try that?
Regards, -- Ilya Kasnacheev пт, 27 нояб. 2020 г. в 17:13, Wolfgang Meyerle < [email protected]>: > Hi, > > after spending several hours to get the unixodbc driver up and running I > nearly gave up. > > However together with the author of unixodbc I was able to find out that > the current odbc driver in Apache Ignite is not doeing what it's > supposed to do. > > As soon as I execute the command: > et = SQLConnect(dbc, (SQLCHAR*)DSN, SQL_NTS, (SQLCHAR*)"", SQL_NTS, > (SQLCHAR*)"", SQL_NTS); > > I get a crash in my program stating that: > isql: symbol lookup error: /usr/local/lib/libignite-odbc.so: undefined > symbol: SQLGetPrivateProfileString > > According to the author of unixodbc this is a function which is called > to find out where to connect to by opening the /etc/odbc.ini file an > looking for the DSN provided by the parameter. > > > I compiled the Apache Ignite odbc connector exactly as stated in the > manual. However an ldd on the /usr/local/lib/libignite-odbc.so does not > show me a dependency on the odbcinst.so as stated by the author. > > So it seems that the configure script for the compilation is broken > somehow. > > I installed unixodbc-dev on my ubuntu box so that shouldn't be the problem. > > Digging down into the cmake script it seems that it also correctly > detects the installed unixodbc-dev installation. > > But the dependency to the odbcinst.so is missing. > > > Hopefully someone can help. > > In the meantime I'm using the SQLDriverConnect routine which is not > dependent on the SQLGetPrivateProfileString. That works but it just a > dirty workaround and shouldn't be the final solution. > > Which ODBC Version is implemented in the code? > > Version2 or Version3? > > Reagards, > > Wolfgang > > > >
