Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f17JoEx95321; Wed, 7 Feb 2001 14:50:15 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f17Jo4907941; Wed, 7 Feb 2001 14:50:04 -0500 (EST) To: Peter Eisentraut cc: pgsql-hackers@postgreSQL.org, pgsql-interfaces@postgreSQL.org Subject: Re: pgAccess fails to launch on HPUX In-reply-to: References: Comments: In-reply-to Peter Eisentraut message dated "Wed, 07 Feb 2001 20:20:16 +0100" Date: Wed, 07 Feb 2001 14:50:04 -0500 Message-ID: <7937.981575404@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200102/242 X-Sequence-Number: 4373 Peter Eisentraut writes: > Tom Lane writes: >> Does anyone object if I modify pgaccess so that it always specifies the >> full path to the library? > If I had known that this was possible I would have done it myself already. > ;-) This is a good idea in general because in a default installation > pgaccess won't find libpgtcl on any system because it doesn't have the > benefit of the -rpath/-R business. Right, even with a cooperative Tcl+kernel, you need to set LD_LIBRARY_PATH to make pgaccess work. Perhaps this will fix that. AFAICT, specifying a full path in the Tcl 'load' command is legal on all systems. However, we still have to rely on the dynamic linker to do the right thing with the indirect dependency on libpq.so, so there may be systems that still need LD_LIBRARY_PATH to find libpq.so. > Please review/remove the note at the > end of the pgaccess ref page if you fix this to your satisfaction. Thanks for the pointer, I probably wouldn't have noticed that. But given the above consideration, I'm not sure I want to remove the note yet. BTW, I'm also thinking about fixing pgaccess so that it honors the --with-pgport configure setting and PGPORT environment variable, rather than having the default port number 5432 hard-wired in. regards, tom lane