Error Unixodbc Library Odbcinst Not Found
Contents |
Regional lists Associations User groups Project lists pgadmin-hackers pgadmin-support pgsql-jdbc pgsql-odbc pgsql-pkg-debian pgsql-pkg-yum psycopg Inactive configure error unixodbc library odbcinst not found lists IRC Local User Groups Featured Users International Sites
Odbcinst Command Not Found
Propaganda Resources Weekly News Re: Fwd: configure: error: unixODBC library "odbcinst" not found while unixodbc odbcinst ini trying to compile odbc From: onur gulsevgi
Odbc_config
error: unixODBC library "odbcinst" not found while trying to compile odbc Date: 2013-07-23 14:39:32 Message-ID: CAOVLFwhKUqkD=u8WDEAsXiKrJ1_qiDDroKcYqvaGqcSz+XmFzQ@mail.gmail.com (view raw or whole thread) Thread: 2013-06-29 05:50:43 from onur gulsevgi
Regional lists Associations User groups Project lists pgadmin-hackers pgadmin-support pgsql-jdbc pgsql-odbc pgsql-pkg-debian pgsql-pkg-yum psycopg Inactive lists IRC Local User Groups Featured Users International Sites Propaganda Resources Weekly News Re: Fwd: configure: error: unixODBC library "odbcinst" not found while trying to compile odbc From: Dev Kumkar
♦ Locked 6 messages Mike Landl Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ unixODBC http://postgresql.nabble.com/unixODBC-library-quot-odbcinst-quot-not-found-when-configuring-psqlodbc-09-01-0100-td5763505.html library "odbcinst" not found when configuring psqlodbc-09.01.0100 Apologies if this has http://www.unixodbc.org/odbcinst.html already been asked and solved.I am trying to build psqlodbc-09.01.0100.tar from source on Red Hat ES 6.3, gcc version 4.4.7-3. When I run "./configure -without-libpq" it fails with the following output:./configure --without-libpqchecking for a BSD-compatible install... /usr/bin/install -cchecking whether build environment is sane... yeschecking for a not found thread-safe mkdir -p... /bin/mkdir -pchecking for gawk... gawkchecking whether make sets $(MAKE)... yeschecking whether to enable maintainer-specific portions of Makefiles... nochecking for style of include used by make... GNUchecking for gcc... gccchecking whether the C compiler works... yeschecking for C compiler default output file name... a.outchecking for suffix of executables...checking whether we are cross compiling... nochecking for error unixodbc library suffix of object files... ochecking whether we are using the GNU C compiler... yeschecking whether gcc accepts -g... yeschecking for gcc option to accept ISO C89... none neededchecking dependency style of gcc... gcc3checking for gcc... (cached) gccchecking whether we are using the GNU C compiler... (cached) yeschecking whether gcc accepts -g... (cached) yeschecking for gcc option to accept ISO C89... (cached) none neededchecking dependency style of gcc... (cached) gcc3checking build system type... x86_64-unknown-linux-gnuchecking host system type... x86_64-unknown-linux-gnuchecking for a sed that does not truncate output... /bin/sedchecking for grep that handles long lines and -e... /bin/grepchecking for egrep... /bin/grep -Echecking for fgrep... /bin/grep -Fchecking for ld used by gcc... /usr/bin/ldchecking if the linker (/usr/bin/ld) is GNU ld... yeschecking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -Bchecking the name lister (/usr/bin/nm -B) interface... BSD nmchecking whether ln -s works... yeschecking the maximum length of command line arguments... 1966080checking whether the shell understands some XSI constructs... yeschecking whether the shell understands "+="... yeschecking for /usr/bin/ld option to reload object files... -
DataManager). This document is aimed at these people and hopes to explain what you need to do and when to do it. What's a ini file ? ODBC first appeared within Windows 3.0. At this time Windows used .ini files to contain configuration information. These are text files containing the following layout [section1] entry1 = value entry2 = value [section2] entry1 = value entry2 = value ... With the advent of Windows NT these ini files have been replaced by the registry, but the API to access them in ODBC has remained the same. Windows has two function in odbcinst.dll that allow applications and drivers to query and modify these files, SQLGetPrivateProfileString and SQLPutPrivateProfileString. As part of unixODBC's aim of reproducing the ODBC environment on non Windows platform's the ini files and libodbcinst provide the same format and functionality. System versus User ODBC distingushes between two types of ini files. System ini files are designed to be accessable but not modifable by any user, and user files are private to a particular user, and may be modified by that user. The system files are odbcinst.ini and odbc.ini (note no leading dot), and the user file is ~/.odbc.ini in each user's home directory (note leading dot). The system file odbcinst.ini contains information about ODBC drivers available to all users, and the odbc.ini file contains information about DSN's available to all users. These "System DSN's" are useful for application such as web servers that may not be running as a real user and so will not have a home directory to contain a .odbc.ini file. A good example of this is Apache and PHP with ODBC support. When the http server is first started it calls SQLAllocEnv as root. it then at a later time changes to the specified user (in my case nobody) and calls SQLConnect. If the DSN's was not a system DSN then this fails. FILEDSN's ODBC 3 also has a third sort of DSN, a file DSN. These store the connection information in a file that may be accessable to anyone. unixODBC does not at this time support FILEDSN's but it will when I get around to it. They are useful things but of less use to UNIX's than NT. Because of the MS view that everyone should have Windows on their desk, each workstation will have it's own registry with it's ow