| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net>, Eddie Stanley <eddiewould(at)paradise(dot)net(dot)nz>, mux(at)elvis(dot)mu(dot)org |
| Subject: | Re: Frustrating issue with PGXS |
| Date: | 2007-06-27 14:10:05 |
| Message-ID: | 15995.1182953405@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> writes:
>> What was the problem with just making all uses of pg_config in
>> Makefile.global use a hardcoded bindir directly?
> Because bindir is given by pg_config:-)
> ISTM that the underlying issue, which was not foreseen in the initial pgxs
> and fixed later, is that some distributions use a different installation
> prefix at compile time and once the software is actually installed.
Right, the installation tree is supposed to be relocatable. Otherwise
we would not need to use pg_config to find the paths at all; we'd just
hardwire all of them when constructing Makefile.global.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-06-27 14:12:53 | Re: Frustrating issue with PGXS |
| Previous Message | Michael Enke | 2007-06-27 12:08:43 | self defined data type "with limit"? |