From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Marti Raudsepp <marti(at)juffo(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL 9.3 beta breaks some extensions "make install" |
Date: | 2013-05-16 13:51:48 |
Message-ID: | 12797.1368712308@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 05/16/2013 05:41 AM, Dimitri Fontaine wrote:
>> And VPATH building of extension is crucially important for me, as the
>> easiest way I've found to build and package a given extension against
>> all currently supported version of PostgreSQL.
> Is there documented support for VPATH builds?
The core code certainly builds okay in VPATH mode, and I would agree
with Dimitri that pgxs builds should as well. But this is more of an
autoconf+make feature than ours, so I'm not sure why you'd expect us
to document it.
Having said that, if a particular extension's makefile contains features
that cause it to not build VPATH, then presumably that extension's
author doesn't care.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2013-05-16 13:52:55 | Re: plperl segfault in plperl_trusted_init() on kfreebsd |
Previous Message | 'Bruce Momjian' | 2013-05-16 13:47:21 | Re: 9.3 Beta1 status report |