[unixODBC-support] driver logging

Eric Sharkey sharkey at netrics.com
Fri Mar 4 17:02:01 GMT 2005


> >Can you "nm -D" your libodbcinst?  Is your build
> >exporting the ini functions?
>
> 00007f18 T iniAllTrim
> 00008008 T iniAppend
> 000082c8 T iniClose

Ah, so it is.

And the 2.2.11 tarball builds ok for me (once I kick sqp/lex.c the same
way I had to kick it for 2.2.10...)

So the difference is aclocal/automake?

diffing the generated Makefiles...

Hmm, I saw this before when I tried (and failed) to build unixODBC-2.2.10
Debian packages.  The problem seems to be shared library extension
detection.

The Makefile built on my system from cvs has:

SHLIBEXT = 

while the one from the tarball has

SHLIBEXT = .so

and this seems to be causing the problem.  I'm not sure what the root
cause of this is yet.

Eric



More information about the unixODBC-support mailing list