Re: mac install question

From: "Dave Page" <dpage(at)pgadmin(dot)org>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "epicwinter(at)hotmail(dot)com" <epicwinter(at)hotmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: mac install question
Date: 2008-08-13 07:44:28
Message-ID: 937d27e10808130044s13cb2568u16d420d62a854eb3@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Jul 24, 2008 at 6:51 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Dave Page <dpage(at)pgadmin(dot)org> writes:
>>> What are you using it for that you need it to be present at install
>>> time?
>
>> The linker hardcodes library paths into exes and libs. We examine
>> these paths at install time using otool and rewrite them from the
>> staging paths on the build machine to whatever directory the user
>> chose to install to using install_name_tool(1).
>
>> The other option would be to rewrite the paths to be relative at build
>> time I guess.
>
> Relative paths sound like the best solution to me, assuming they work.

For info, the latest version of the installer (download from
http://www.enterprisedb.com/products/pgdownload.do) fixes this
problem.

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bartels, Eric 2008-08-13 08:06:37 Postgres eats all memory
Previous Message Daneel 2008-08-13 07:25:35 Re: Newbie [CentOS 5.2] service postgresql initdb