From: Lamar Owen <lamar.owen@wgcr.org>
Organization: Little to None
To: "Nigel Berkeley" <nige@incagold.com>, <pgsql-interfaces@hub.org>
Subject: Re: [INTERFACES] PgAccess 0.98 and libpq.so.2
Date: Fri, 26 Nov 1999 11:23:46 -0500
Content-Type: text/plain
References: <003201bf3617$03e43b60$77e793c3@mercury>
	<383C2EFA.52F08591@wgcr.org>
	<003201bf36e0$3e93a1a0$5318063e@mercury>
In-Reply-To: <003201bf36e0$3e93a1a0$5318063e@mercury>
MIME-Version: 1.0
Message-Id: <99112611472202.00541@lorc.wgcr.org>
Content-Transfer-Encoding: 8bit

On Wed, 24 Nov 1999, Nigel Berkeley wrote:
> run pgaccess, or worse still theres going to be A LOT of people that
> arnt able to use pgaccess at all because they dont know what the
> problem is!
> 
> Constantin, if it is the case of not having the old lib, are you
> planning to update pgaccess to use libpq.so.2?

The pgaccess tcl/tk script does not require any library other than libpgtcl.so
-- it's libpgtcl.so that requires a specific libpq.so.

Checking my installation of PostgreSQL (that I installed from sources via
building the RPM set), libpgtcl.so from 6.5.3 does NOT require libpq.so.1 -- it
requires libpq.so.2) (the output from 'ldd /usr/lib/libpgtcl.so' will tell you
what libraries it depends upon -- here's the output of 'ls -l
/usr/lib/libpgtcl.*' , followed by the output of 'ldd /usr/lib/libpgtcl.so' --
note that your installation of PostgreSQL has different directories for these
-- and make double sure that there is no other libpgtcl.so on your system in a
library search path):
-------------ls -l /usr/lib/libpgtcl.* ------------
-rw-r--r--   1 root     root        27260 Nov  4 22:30 /usr/lib/libpgtcl.a
lrwxrwxrwx   1 root     root           15 Oct  9 23:11 /usr/lib/libpgtcl.so -> libpgtcl.so.2.0
lrwxrwxrwx   1 root     root           15 Oct  9 23:11 /usr/lib/libpgtcl.so.2 -> libpgtcl.so.2.0
-rwxr-xr-x   1 root     root        28276 Nov  4 22:30 /usr/lib/libpgtcl.so.2.0
----------------------------------------
------------ldd /usr/lib/libpgtcl.so-------------
	libpq.so.2.0 => /usr/lib/libpq.so.2.0 (0x4000d000)
	libcrypt.so.1 => /lib/libcrypt.so.1 (0x4001a000)
	libc.so.6 => /lib/libc.so.6 (0x40047000)
	/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
----------------------------------------

I have built RPM's for 6.5.x many different times on RedHat 5.2 and RedHat 6.1,
and I have never had this problem you are having.  Building the RPM's, as I
have said, involves configure'ing, make'ing, and 'make install'ing just like
you have done, just with a slightly different set of configure options (in
particular,  prefix is set to a different value than the norm).  Make double
and triple sure that the old PostgreSQL 6.3.2 RPM's are not installed -- or
that artifacts from the 6.3.2 RPM install aren't left on the disk.

Summary: if you have a version of libpgtcl.so on your system (look for
/usr/lib/libpgtcl.* -- the 6.3.2 RPM shipped a /usr/lib/pgtcl.so.1, that was
symlinked from /usr/lib/libpgtcl.so, IIRC) that requires libpq.so.1 (which the
version of libpgtcl.so that ships with 6.5.3 does NOT), then this error will
show. 

A copy of the 'rpm -qa' output from your machine would be helpful -- send it to
me directly, and not to the list, as the output is large.

HTH

--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11