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

Re: [INTERFACES] pgAccess fails to launch on HPUX

From: "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org, pgsql-interfaces(at)postgresql(dot)org
Subject: Re: [INTERFACES] pgAccess fails to launch on HPUX
Date: 2001-02-07 18:49:13
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-interfaces
On Wed, Feb 07, 2001 at 01:34:58PM -0500, Tom Lane wrote:
> I thought I'd tried pgAccess back in the dim past with success, but as
> of current sources it fails on HPUX 10.20 and Tcl 8.3.2:
<SNIP problem with dynamic load and Tcl>

> And the reason for *that* is that Tcl doesn't pass the DYNAMIC_PATH flag
> to shl_load().  I find that already has a couple of bug
> reports posted on this, so perhaps the Tcl guys will get their act
> together and add the flag in Tcl 8.4, but in the meantime I think we
> have very little choice except to specify the full path to the library
> in pgaccess' load command.

Yep, the Tcl team changed dynamic loading in 8.2->8.3 This bit me on NT,

> Does anyone object if I modify pgaccess so that it always specifies the
> full path to the library?  That seems like it'd be a good idea even on
> OSes without this quirk, because it'd ensure getting the matching
> version of libpgtcl and libpq even if your SHLIB_PATH/LD_LIBRARY_PATH
> points to some other version.

Sounds like a good idea, to me. Getting the wrong library loaded leads to
non-obvious error messages, as well.


In response to


pgsql-hackers by date

Next:From: Larry RosenmanDate: 2001-02-07 18:58:15
Subject: RE: python build/Current CVS/UnixWare
Previous:From: Peter EisentrautDate: 2001-02-07 18:43:06
Subject: Re: unixODBC (again)

pgsql-interfaces by date

Next:From: Bruce MomjianDate: 2001-02-07 19:12:26
Subject: PostgreSQL and PHP persistent connections
Previous:From: Tom LaneDate: 2001-02-07 18:34:58
Subject: pgAccess fails to launch on HPUX

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