Re: moving an installation

OK, I see the problem is in the share/conversion_create.sql script,
which references $libdir as part of the library path. So modifying the
script and replacing $libdir with an actual path fixes the problem,
allowing initdb to run.

But is there any way around this without actually modifying the script?
e.g., an environment variable or something? (setting the "libdir" env
var doesn't seem to do it).

Thanks.

- DAP

-----Original Message-----
From: pgsql-general-owner(at)postgresql(dot)org
[mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of David Parker
Sent: Thursday, July 15, 2004 4:05 PM
To: pgsql-general(at)postgresql(dot)org
Subject: [GENERAL] moving an installation

I need to be able to build postgres (7.4.3) with a given --prefix, but
then pack up the installation directory and deploy it in another
directory (as part of a product install, for instance).

I configured with --disable-rpath, but I'm still getting the

creating conversions... ERROR: could not access file
"$libdir/ascii_and_mic": No such file or directory

error when I try to run initdb from the new location. This is on Solaris
9, and I've verified that my LD_LIBRARY_PATH includes the postgres/lib
dir in the new location.

Is there a way I can get around this at runtime? I was under the
impression that --disable-rpath prevented library paths from being
compiled into the code, but maybe this "$libdir" is a different thing?

Thanks in advance for any help.

- DAP
======================================================
David Parker Tazz Networks (401) 709-5130

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings