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

Re: [INTERFACES] pgAccess fails to launch on HPUX

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Constantin Teodorescu <teo(at)flex(dot)ro>
Cc: "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>, 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 21:42:08
Message-ID: 10989.981582128@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-interfaces
Constantin Teodorescu <teo(at)flex(dot)ro> writes:
> Yes. The full path to libpgtcl might be specified directly in pgaccess.

I have committed pgaccess changes to do this.

> But libpq library need to be found automatically because it isn't in a "load"
> explicit command.

At least on HPUX 10, this seems to work anyway, presumably because the
correct search path is embedded into libpgtcl.sl.  I imagine that not
all platforms have 'rpath' info embedded into shlibs, so there may be
other platforms where you still need to set LD_LIBRARY_PATH to find
libpq.so.

Thought: would it be out of line for pgaccess.sh to set LD_LIBRARY_PATH
explicitly to cover this possibility?

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Peter MountDate: 2001-02-07 22:05:23
Subject: Re: CORBA?
Previous:From: Oliver ElphickDate: 2001-02-07 21:36:31
Subject: Utility program to read parameters of the current database

pgsql-interfaces by date

Next:From: Peter MountDate: 2001-02-07 22:07:28
Subject: Re: PostgreSQL and PHP persistent connections
Previous:From: Peter MountDate: 2001-02-07 21:41:43
Subject: Re: PostgreSQL and PHP persistent connections

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