David Parker wrote:
> allows initdb and createdb to run, which was my initial stumbling
> block. I haven't done anything in particular with the resulting
> database yet. Do you expect the installation to break in other
> places?
Off the top of my head, at least createlang, pg_dumpall, and ecpg wil
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> David Parker wrote:
>> 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).
> This doesn't work.
Not at t
CTED]
Sent: Thursday, July 15, 2004 5:33 PM
To: David Parker; [EMAIL PROTECTED]
Subject: Re: [GENERAL] moving an installation
David Parker wrote:
> 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 anothe
David Parker wrote:
> 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
This doesn't wo
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 scr
