+-------------------------------------------------------------+
| unixODBC                                                    |
+-------------------------------------------------------------+

README
---------------------------------------------------------------

Description:

	unixODBC is an Open Source ODBC sub-system and an ODBC SDK
	for Linux, Mac OSX, and UNIX.

License:

	All libraries are LGPL Version 2.1

	All programs are GPL Version 2.1.

Parts:
	unixODBC includes the following;

	- Driver Manager
	- Installer Library and command line tool
	- Command Line Tools to help install a driver and work with SQL


How To Start:

	Look for and read README files with extensions of interest. Then
	read the INSTALL file.

	You can also jump into the doc directory and browse information
	there. And do not forget the online stuff.

	Some documentation may be a bit out of date the vast majority of
	it should be ok.

Config Files:

	The ODBC Installer Library is responsible for reading and writing
	the unixODBC config files.

	The savvy can look at;

	_odbcinst_SystemINI.c
	_odbcinst_UserINI.c

	In any case; you can override where unixODBC looks for its system
	config files by setting the ODBCSYSINI environment variable during
	the use of unixODBC.

Resources:

        http://sourceforge.net/projects/unixodbc/

Building on AIX
===============

Install
=======

AIX seems to ship with a install tool /usr/bin/bsdinstall, unfortunatly
the version of autoconf that unixODBC uses doesn't seem to like this, so
make sure it doesn't find this. It may be best to define INSTALL as a
empty string before building, forcing it to use the builtin install-sh.

Threads
=======

You need to decide to build with or without threads, if you want threads
I would do this

export CC=xlc_r
export CXX=xlC_r
./configure

If you don't want threads, do this

export CC=xlc
export CXX=xlC
./configure --enable-threads=no

Shared Libs
===========

Because of the way that AIX builds its shared libs there are a couple of
points to remember

1. All drivers need changing into .so

The drivers will be build as a .a, containing a .so, BUT dlopen only is
able to open a .so, so to fix this, for each driver that is needed, do
the following (in this case the postgres driver).

Go to the target lib directory

	cd /usr/local/lib

extract the .so from the .a

	ar -x libodbcpsql.a

This will create libodbcpsql.so.2

The same will need doing for the seyup libs

	ar -x libodbcpsqlS.a

2. Shared libs containing C++ are special

This is only a issue with the libodbcinstQ.a lib that is opened by
ODBCConfig. There are two things, first because libtool decides that
shared libs ar lib*.a the code trys to load libodbcinstQ.a, and also
we maye have to rebuild the lib using the IBM util makeC++SharedLib
(the name gives its away :-)

I have tried this with a current AIX, and it seems that all is needed is to extract the .so
from the .a by running ar -x libodbcinstQ.a to get the .so

If that doesn't help, or on older AIX's the following may need doing.

After the make install is done, go into the odbcinstQ dir on thE
build tree, and do the following

	makeC++SharedLib -p 0 -o libodbcinstQ.so.1.0 -L$QTDIR/lib -lqt -L$PREFIX/lib -lodbc -lodbcinst  .libs/libodbcinstQ.lax/libodbcextraslc.al/strcasecmp.o  *.o ../ini/*.lo

where QTDIR is set to the top of the qt tree, so $QTDIR/lib will contain libqt.a
and PREFIX is set to the unixODBC install tree, so $PREFIX/lib contains libodbc.a.
Ignore any duplicate symbol warnings they are due to the same things being in libodbc.a
and libodbcinst.a

this will then build a libodbcinstQ.so.1.0, we can copy that to the target lib dir,
and delete the existing lib, and link it (again replace $PREFIX with the correct path

	cp libodbcinstQ.so.1.0 $PREFIX/lib
	cd $PREFIX/lib
	rm libodbcinstQ.a
	ln -s libodbcinstQ.so.1.0 libodbcinstQ.a

Then all should be OK with ODBCConfig

Nick Gorham

To build unixODBC on cygwin, all you need to do is to rerun the autoconf
tools to create versions that seem to play on windows, then build as normal.

Of course to do this you need to have installed the Cygwin development
packages.

So:

	aclocal
	automake --add-missing
	automake
	autoconf
	libtoolize --copy --ltdl --force

Then you can run configure as normal

	./configure --enable-gui=no
	make
	make install

At least that seems to work when I tried it... If you find problems
just let me know.

--
Nick Gorham (nick.gorham@easysoft.com)

Some notes on building UnixODBC on Microsoft Interix

First use the modified configure and config.guess
included in the Interix directory, copy them up into the main
directory.

Then build with the following line

CFLAGS="-D_ALL_SOURCE -I/usr/local/include" CPPFLAGS="-D_ALL_SOURCE
-I/usr/local/include" LDFLAGS="-L/usr/local/lib" ./configure

After running configure, copy libtool from the Interix directory
into the build directory

Thanks to the MS group for supplying this info.

Thats all for now.

Nick.

+-------------------------------------------------------------+
| unixODBC                                                    |
| Mac OSX                                                     |
+-------------------------------------------------------------+

README
---------------------------------------------------------------

It seems at least with 10.5 of OSX, that we can just configure as
normal (--enable-gui=no) and build, no special instructions are
needed.

---------------------------------------------------------------

Building With GNU Auto Tools (by Nick):

	It looks as if Darwin (Mac OSX) doesn't support the normal
	dlopen type process that unixODBC requires. However help is
	at hand in the form of dlcompat-20010831.tar.gz. This file
	contains wrappers to emulate the calls. I have put this in

	ftp://ftp.unixodbc.org/pub/beta/unixODBC/dlcompat-20010831.tar.gz

	It should be downloaded, unpacked then run make install

	This should be done before configuring unixODBC

	This file was created by Christoph Pfisterer <cp@chrisp.de> and
	the original copy can be found at

	    http://fink.sourceforge.net

	If you get a "ld: multiple definitions of symbol " error,
	then you should edit the file libtool in the unixODBC base
	directory and find the line

	    whole_archive_flag_spec="-all_load \$convenience"

	and replace it with

	    whole_archive_flag_spec=

	As at the time of writing, Qt is not available on OSX, its best to
	disable the search for X libs that may fail, by configuring with

	    ./configure --enable-gui=no

Problems:

    There is a problem it seems with libtool on OSX that incorrectly sets
    the SHLIBEXT. The Driver Manager code will now report this if its used
    in this condition. There are two solutions. Either after running configure
    check config.h, and search for the string SHLIBEXT. It should look like this:

#define SHLIBEXT ".dylib"

    But may look like this:

#define SHLIBEXT "test .$module = .yes && echo .so || echo .dylib"

    If it does, then change it to the first definition.

    The other fix is to change the configure script to find the correct value,
    search for the line:

shrext_cmds='test .$module = .yes && echo .so || echo .dylib'

    And change to

shrext_cmds=`test .$module = .yes && echo .so || echo .dylib`

    Then rerun configure


Building With Qt qmake (by Peter):

	Qt is now availible for OSX but unixODBC may not detect your Qt
	libs... worse yet you may not be able sort out the GNU auto-tools
	required to build on OSX.

	If you want to build using qmake then read README.qmake.


Creating Install Packages:

	unixODBC contains a number of directories and files to help create
	OSX Packages. The process of doing so is not nearly as automated
	as creating RPM files using the GNU auto tools. Look for the
	mac-install and mac-package directories.

Cursor LIB

The cursor lilb needs a manual stage build to create it as a OSX bundle
it needs to be like that so the DM can load it at run time.

To do this, after the "make" and "make install" have finished, go to the
cur directory in the build tree. Then there issue these commands

cc -bundle -flat_namespace -undefined suppress -o libodbccr.1.0.0.so *.lo
cp libodbccr.1.0.0.so /usr/local/lib/libodbccr.1

Replace /usr/local/lib/ in the above with whatever your actual unixODBC
lib path is.

You may also have to do the same with any driver you build. You can check
this by testing the type of the lib, for example.

file /usr/local/lib/libodbcpsql.2.0.0.so
/usr/local/lib/libodbcpsql.2.0.0.so: Mach-O dynamically linked shared library ppc

This is not the correct type.

So to get it as you need :-

cd Drivers/Postgre7.1
cc -bundle -flat_namespace -undefined suppress -o libodbcpsql.2.0.0.so *.lo
cp libodbcpsql.2.0.0.so /usr/local/lib/libodbcpsql.2.0.0.so

Now to check

file /usr/local/lib/libodbcpsql.2.0.0.so
/usr/local/lib/libodbcpsql.2.0.0.so: Mach-O bundle ppc

Thats how it should be to work under the driver manager

+-------------------------------------------------------------+
| Peter Harvey <pharvey@codebydesign.com>                     |
| Added to by Nick Gorham <nick@lurcher.org>                  |
+-------------------------------------------------------------+

Building unixODBC on QNX
========================

This has been tested on the QNX 6.1 x86 release.

1. unpack the distribution, and cd into the distribution dir

2. Add any missing files

	automake --add-missing

3. Configure unixODBC

	./configure --sysconfdir=/etc --enable-gui=no --prefix=/opt

4. run libtooloze using the QNX version of libtool, then update aclocal.m4

	libtoolize --force
	aclocal

5. We now need to alter the flags dlopen uses

	cd libltdl
	sed "s/RTLD_GLOBAL/RTLD_GROUP/" ltdl.c > ltdl.c.new
	sed "s/RTLD_LAZY/RTLD_NOW/" ltdl.c.new > ltdl.c
	cd ..

6. Force a reconfigure

	rm config.cache

7. Make, then install

	make
	make install

And with luck and a trailing wind, that should be that.

EXTRA STUFF for QNX 6.2, if the wind is head on...

If you find that it segfaults, its worth going into the libltdl
directory, editing the Makefile, and changing the line

CFLAGS = -g -O2

to

CFLAGS = -g -O2 -DPIC -fPIC

then touch ltdl.c to force a rebuild

You may also get a error when building in the exe directory, to
fix this, go to the exe directory, edit Makefile, and change

OBJEXT = @OBJEXT@

to

OBJEXT = o

And

EXEEXT = @EXEEXT@

to

EXEEXT =

Building unixODBC on Solaris
----------------------------

This should just work, however I have had the following helpfull
hints sent to me by David Brown of Starquest. The suggested change
has been made to the code in __info.c

"Last fall, I had problems running on Solaris 7, because my system did have
an iconv conversion between ISO8859-1 and UCS-2.

I discovered two things:

* the missing iconv tables are available by a patch for Solaris 7 (there is
also a corresponding patch for Solaris 8, that fixes a lot in this area -
seems recommended to use that as well)

* Solaris uses the name 8859-1 in its tables rather than ISO8859-1 or
ISO-8859-1.


So what I've done is:

1) make the following change to DriverManager/__info.c:

diff __info.c __info.c.orig
385c385
<     char *asc[] = { "char", "ISO8859-1", "ISO-8859-1", "8859-1", "ASCII", NULL
 };
 ---

 >>     char *asc[] = { "char", "ISO8859-1", "ISO-8859-1", "ASCII", NULL };

 2) tell customers to apply the following Solaris patches:

 Solaris 7:
 Patch-ID# 112689-02
 Keywords: UTF-8 ICONV
 Synopsis: SunOS 5.7: UTF-8 locale ICONV patch
 Date: Aug/28/2002

 Solaris 8:
 Patch-ID# 113261-01
 Keywords: UTF-8 ICONV
 Synopsis: SunOS 5.8: UTF-8 locale ICONV patch
 Date: Oct/11/2002

 this has since been superceded by 11326-02, but I think unixODBC should
 function fine with 113261-01

 Patch-ID# 113261-02
 Keywords: UTF-8 ICONV
 Synopsis: SunOS 5.8: UTF-8 locale ICONV patch
 Date: Feb/21/2003"

Building unixODBC on OpenVMS (non-VAX only)
=========================================

Here's an initial go at building unixODBC on OpenVMS, at present this will
only run on alpha and itanium, but if anyone requires use of this on VAX drop me an email
(suypport@easysoft.com) and I'll do the necessary transfer vector macro's to export
the required symbols from the two shared objects (ODBC.EXE and ODBCINST.EXE).

Current components which have been built on OpenVMS

LIBODBC.OLB 	   Driver manager as an OpenVMS static object library
LIBODBCINST.OLB    ODBC installer / setup static object library
LIBODBCPSQL.OLB    Postgres 6.5 driver static object library
LIBODBC.EXE        Driver manager shareable image
LIBODBCINST.EXE    ODBC installer / setup shareable image
LIBODBCPSQL.EXE    Postgres 6.5 driver shareable image
ISQL.EXE           Command line SQL tool
DLTEST.EXE         Program to test loading shared libraries

Additional components included to perform building on OpenVMS

VMSBUILD.COM - DCL script which compiles, links and installs unixODBC
[.EXTRAS]VMS.C  - Contains OpenVMS specific wrappers (dlopen, etc..)
[.VMS]INSTALL_IMAGE.COM - DCL script to install shareable images
[.VMS]ODBCINST_AXP.OPT - Linker options file for ODBC installer shared image
[.VMS]ODBC_AXP.OPT - Linker options file for Driver manager shared image
[.VMS]ODBC2_AXP.OPT - Linker options file for ODBC 2 drivers
[.VMS]ODBC_SETUP.COM - DCL script to set up logicals and commands

Building unixODBC on OpenVMS
============================

After unpacking the archive, change into the unixodbc directory and perform
the following functions.

COMPILING

$ @vmsbuild COMPILE

LINKING

$ @vmsbuild LINK

COPYING SHARED LIBRARIES TO THEIR INSTALLED LOCATION

Define the logical name ODBC_LIBDIR to point to wherever you would like the
libraries to reside and run the build procedure again with the "install" option
as in the following example:

$ define ODBC_LIBDIR DISK$DBSTUFF:[ODBCLIB]  ! will be created if it doesn't exist
$ @vmsbuild install

If the ODBC_LIBDIR logical is not defined, it will be defined for you
and a [.odbclib] directory will be created under the top level of the
source directory.

Note that the build procedure can be run in batch if you prefer.  It is
also possible to specify ALL as the parameter and do the compile, link,
and install in one fell swoop.  For example:

$ submit/noprint/param=all vmsbuild.com

Post-installation tasks
======================================

To use the installed software, you need to run the command procedure
ODBC_SETUP.COM, which will have been installed in the same directory as
the libraries.  This procedure defines the ODBC_LIBDIR logical name and
additional logical names that are needed for the image activator to
locate the libraries.  It also defines the ISQL command.  Put a line
similar to the following (with your own disk and directory
specification) in your LOGIN.COM, or (to make the software available
system-wide) in SYS$MANAGER:SYLOGIN.COM:

$ @disk$dbstuff:[odbclib]odbc_setup

N.B.  It may be tempting to simply dump the libraries into SYS$SHARE and
depend on the image activator's default behavior to locate the images.
That works, but it's the surest way to what is known on another popular
platform as DLL hell.

If you'll be programming with ODBC rather than just using ISQL, be sure
to hang on to the contents of the [.include] and [.doc] directories.
Look at the compiler flags and link commands in vmsbuild.com for
examples of what you need to do to build programs using the libraries.

For performance reasons it may be desireable to install the libraries as
known images (which has nothing to do with "install" in the sense of
copying software to its target location).  See the documentation to the
INSTALL command or use the command procedure [.vms]install_image.com
provided with this kit.  Installing the images with privileges is not
recommended unless there is a compelling reason (Hint: failure to set up
file permissions properly on your .ini files is not a compelling
reason).

Locations of ODBC.INI and ODBCINST.INI
======================================

After running the @VMSBUILD INSTALL command a blank odbc.ini and odbcinst.ini
will be created in ODBC_LIBDIR. To override the default locations of the user
odbc.ini or the directory where the system odbc.ini and odbcinst.ini reside
define the following logicals.

$ define/log ODBCINI "DKA100:[MYDIR.ODBC]ODBC.INI"
$ define/log ODBCSYSINI "DKA100:[MYDIR.SYS]"

Example Setup With Postgres 6.5
===============================

ODBC_LIBDIR:ODBCINST.INI

[PostgreSQL]
Description = Postgres SQL Driver
Driver      = LIBODBCPSQL
Setup       =
FileUsage   = 1

ODBC_LIBDIR:ODBC.INI
[Postgres]
Description         = Test to Postgres
Driver              = PostgreSQL
Trace               = No
Database            = sample
Servername          = myserver.mydomain.com
UserName            = postgres
Password            = password
Port                = 5432
Protocol            = 6.4
ReadOnly            = No
RowVersioning       = No
ShowSystemTables    = No
ShowOidColumn       = No
FakeOidIndex        = No
ConnSettings        =

Jason

last updated 12-Jul-2013 by Craig A. Berry -- craigberry@mac.com