configure error unixodbc library odbcinst not found
Regional lists Associations User groups Project lists pgadmin-hackers pgadmin-support pgsql-jdbc pgsql-odbc pgsql-pkg-debian
Zabbix Configure Error Unixodbc Library Not Foundpgsql-pkg-yum psycopg Inactive lists IRC Local User Groups odbcinst command not found Featured Users International Sites Propaganda Resources Weekly News Re: unixODBC library "odbcinst" not found when configuring psqlodbc-09.01.0100 From: "Mike Landl"
♦ ♦ Locked 14 messages onur gulsevgi Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ configure: error: unixODBC library "odbcinst" not found while trying to compile odbc In a project, I asked to create a database link between Oracle to PostGreSQL. I thought that I can use Oracle’s Heterogeneous Services. https://www.postgresql.org/message-id/00a501ce7e6f$4a982e40$dfc88ac0$@com Oracle Database is running on Sparc Server (Solaris 10), so I downloaded the free ODBC packages from unixODBC project. They already provide a binary package for Solaris but it says it will remove any non pkgmgr content in “/usr/local/bin” directory. So I decided to download the source codes http://postgresql.nabble.com/configure-error-unixODBC-library-quot-odbcinst-quot-not-found-while-trying-to-compile-odbc-td5761814.html and build it manually. Here are the commands to build unixODBC:./configure --prefix=/usr/local/unixODBCmakemake installThen I try to install psqlodbc-9.02.0100 driver with the following command, I get this: oracle->>./configure --prefix=/data11/ora_bosa/bosadb/odbc/driver --without-libpq checking for a BSD-compatible install... config/install-sh -cchecking whether build environment is sane... yeschecking for a thread-safe mkdir -p... config/install-sh -c -dchecking for gawk... nochecking for mawk... no checking for nawk... nawkchecking whether make sets $(MAKE)... yeschecking whether to enable maintainer-specific portions of Makefiles... nochecking for style of include used by make... GNUchecking for gcc... gcc checking 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 suffix of object files... o checking whether we are using the GNU C compiler... yeschecking whether gcc accepts -g... yeschecking for gcc option to accept ISO C89... none neededchecking depende
search in one of my setsExclude this search from one of my sets 8 messages in org.postgresql.pgsql-odbcRe: [ODBC] Fwd: configure: error: uni...FromSent OnAttachmentsonur gulsevgiJun http://markmail.org/message/ybwra3d4ymmdtr2k 28, 2013 10:50 pm Inoue, HiroshiJul 15, 2013 5:26 pm Dev KumkarJul 16, 2013 4:06 am Hiroshi InoueJul 19, 2013 5:12 pm Dev KumkarJul 22, 2013 12:00 pm onur gulsevgiJul 23, 2013 7:39 am Dev KumkarJul 23, http://www.unixodbc.org/odbcinst.html 2013 11:28 am Hiroshi InoueJul 24, 2013 12:37 am Subject:Re: [ODBC] Fwd: configure: error: unixODBC library "odbcinst" not found while trying to compile odbcFrom:Dev Kumkar (devd...@gmail.com)Date:Jul 16, 2013 4:06:44 amList:org.postgresql.pgsql-odbcOn Tue, Jul not found 16, 2013 at 12:13 AM, onur gulsevgi
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 bu