pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Thomas G. Lockhart <lockhart@alumni.caltech.edu>
To: John Sharp <JSharp@cfipro.com>
Cc: pgsql-interfaces@postgresql.org <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] postodbc on sparc2.5.1
Date: Thu, 03 Sep 1998 02:40:39 +0000
Message-ID: <35EE01A7.B204EEA7@alumni.caltech.edu> (raw)
References: <19980902101454994-89c6e9f4@cfipro.com>

> 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



view thread (6+ messages)  latest in thread

Message-ID: <35EE01A7.B204EEA7@alumni.caltech.edu>
Permalink:  ../35EE01A7.B204EEA7@alumni.caltech.edu/
Also on:    postgresql.org/message-id/35EE01A7.B204EEA7@alumni.caltech.edu

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: lockhart@alumni.caltech.edu, JSharp@cfipro.com
  Subject: Re: [INTERFACES] postodbc on sparc2.5.1
  In-Reply-To: <35EE01A7.B204EEA7@alumni.caltech.edu>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox