| 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 17:44:12 |
| Message-ID: | 17097.1354383852@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
=?iso-8859-1?q?C=E9dric_Villemain?= <cedric(at)2ndquadrant(dot)com> writes:
> the attached patch fix the extension installation using a VPATH when a
> MODULEDIR is defined in the extension Makefile.
> The current issue is that the sharedir/extension directory is not created if
> MODULEDIR != 'extension' i.e. MODULEDIR is defined in the Makefile. Thus 'make
> install' fail to copy the control file in an nonexistent directory.
[ 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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cédric Villemain | 2012-12-01 19:33:38 | Re: extension installation faillure using VPATH and MODULEDIR |
| Previous Message | Cédric Villemain | 2012-12-01 14:13:49 | extension installation faillure using VPATH and MODULEDIR |