| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: mac install question |
| Date: | 2008-07-24 02:09:59 |
| Message-ID: | 4887E477.7050408@postnewspapers.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Dave Page wrote:
> 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).
Yep, the mac linker seems to default to absolute rpath linking, which I
personally find *really* frustrating.
> The other option would be to rewrite the paths to be relative at build
> time I guess.
That's the approach most Mac apps take, and is supported by the @
relative path syntax in install_name_tool.
--
Craig Ringer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris | 2008-07-24 03:17:18 | Re: pg_query transaction: auto rollback? begin or start?? commit or end??? |
| Previous Message | Garber, Mikhail | 2008-07-24 01:23:19 | problem installing RPMs on RHEL5 |