From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | cedric(at)2ndquadrant(dot)com |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: extension installation faillure using VPATH and MODULEDIR |
Date: | 2012-12-01 21:06:41 |
Message-ID: | 15395.1354396001@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
=?iso-8859-15?q?C=E9dric_Villemain?= <cedric(at)2ndquadrant(dot)com> writes:
> Le samedi 1 dcembre 2012 18:44:12, Tom Lane a crit :
>> [ scratches head ... ] What's this have to do with VPATH?
>>
>> I see the point that if EXTENSION is set, and a nondefault MODULEDIR is
>> selected, the "install" target puts the control file into the extension
>> subdirectory which hasn't been made by installdirs. But that seems not
>> connected to VPATH builds.
> I just hit the bug and though it was relative to VPATH because it was the main
> difference in my build. Obviously in my others scenariii the extension/
> directory was pre-existent and I didn't notice the problem.
No worries, I was just wondering if you were seeing something more than
the problem described. Committed to 9.1 and up.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2012-12-01 21:46:09 | Re: PITR potentially broken in 9.2 |
Previous Message | Tom Lane | 2012-12-01 20:47:28 | Re: PITR potentially broken in 9.2 |