Skip site navigation (1) Skip section navigation (2)

Re: [INTERFACES] postodbc on sparc2.5.1

From: "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>
To: John Sharp <JSharp(at)cfipro(dot)com>
Cc: "pgsql-interfaces(at)postgresql(dot)org" <pgsql-interfaces(at)postgreSQL(dot)org>
Subject: Re: [INTERFACES] postodbc on sparc2.5.1
Date: 1998-09-03 02:40:39
Message-ID: 35EE01A7.B204EEA7@alumni.caltech.edu (view raw or flat)
Thread:
Lists: pgsql-interfaces
> I have been trying to implement postodbc on a solaris sparc 2.5.1.
> (source distribution from insightdist.com v0249).

psqlodbc?

> I have got it to compile but not load yet.
> SQLColumns now not found.  Note: all functions not found by
> the linker are Window's APIs.

SQLColumns is in info.c, which should be in the distribution.

> Tried linking in the libiodbc.a file.  The linker found the missing
> functions but now SQLError is a multiple define.
> Should I remove the implementation for SQLError in postodbc to
> eliminate the final linker error.  Is this the right way to go, or is
> there some other solution?

Wrong way to go. iODBC should _not_ be linked directly with your
psqlodbc image, because it has duplicate routines for every ODBC API! It
relies on explicit dynamic loading to find the psqlodbc routines at
runtime.

You will need to find the linker options which force your psqlodbc
library to resolve all symbols internally. That way it won't be linked
back to iODBC at runtime (which happened to me on Linux). Don't know
what the options would be for Solaris; on Linux it is -Bsymbolic. I had
to include libc and libm in the link step to resolve the printf and pow
functions used by psqlodbc.

You will also need a decent ~/.odbc.ini file. Let me know if you don't
already have one...

                    - Tom

In response to

Responses

pgsql-interfaces by date

Next:From: Dean NeumannDate: 1998-09-03 03:27:34
Subject: How do I compile libpq++ and odbc?
Previous:From: Peter T MountDate: 1998-09-02 21:44:50
Subject: Re: [INTERFACES] Jdbc and oid

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group