Re: [HACKERS] Making pgxs builds work with a relocated installation

2005-09-28 Thread Tom Lane
Alvaro Herrera <[EMAIL PROTECTED]> writes: > The only question is, do we want to force a Python dependency for > building Postgres? That's not happening. Especially not now that Dave found the other solution does work ... regards, tom lane ---(end

Re: [HACKERS] Making pgxs builds work with a relocated installation

2005-09-28 Thread Alvaro Herrera
On Wed, Sep 28, 2005 at 10:05:48AM +0100, Dave Page wrote: > > Tom Lane wrote: > > > Yuck. Anyone have another idea on coping with space-containing > > > pathnames? > > > > Switch to scons. You heard it here first! > > Oooh, that looks nice at first glance... The only question is, do we want

Re: [HACKERS] Making pgxs builds work with a relocated installation

2005-09-28 Thread Dave Page
> -Original Message- > From: Tom Lane [mailto:[EMAIL PROTECTED] > Sent: 27 September 2005 18:57 > To: Magnus Hagander > Cc: Dave Page; Peter Eisentraut; pgsql-hackers@postgresql.org > Subject: Re: [HACKERS] Making pgxs builds work with a > relocated installation

Re: [HACKERS] Making pgxs builds work with a relocated installation

2005-09-28 Thread Dave Page
> -Original Message- > From: Peter Eisentraut [mailto:[EMAIL PROTECTED] > Sent: 28 September 2005 06:37 > To: Tom Lane > Cc: Magnus Hagander; Dave Page; pgsql-hackers@postgresql.org > Subject: Re: [HACKERS] Making pgxs builds work with a > relocated installatio

Re: [HACKERS] Making pgxs builds work with a relocated installation

2005-09-27 Thread Peter Eisentraut
Tom Lane wrote: > Yuck. Anyone have another idea on coping with space-containing > pathnames? Switch to scons. You heard it here first! -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 2: Don't 'kill -9'

Re: [HACKERS] Making pgxs builds work with a relocated installation

2005-09-27 Thread Tom Lane
"Magnus Hagander" <[EMAIL PROTECTED]> writes: > Using GetShortPathName() will break on any system that has disabled > short filename generatino, which IIRC is a recommended best practice > both for performance and for security in legacy apps. I don't know what > it does, but probably it will just r

Re: [HACKERS] Making pgxs builds work with a relocated installation

2005-09-27 Thread Peter Eisentraut
Tom Lane wrote: > pgxs.mk itself requires access to datadir and docdir, so I don't > see how you can maintain that those aren't necessary. The only > reason it doesn't also reference mandir and localedir is that none of > our current contrib modules have any man pages or locale support, Well, I d

Re: [HACKERS] Making pgxs builds work with a relocated installation

2005-09-27 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > Am Dienstag, 27. September 2005 02:12 schrieb Tom Lane: >> Not all of the path variables set up in Makefile.global are currently >> available from pg_config; the missing ones are >> >> prefix >> exec_prefix >> sbindir >> mandir >> localedir >> libexec

Re: [HACKERS] Making pgxs builds work with a relocated installation

2005-09-27 Thread Peter Eisentraut
Am Dienstag, 27. September 2005 02:12 schrieb Tom Lane: > What I propose we do about this is change the path setup section > of Makefile.global to look like (for each path variable) > > ifdef PGXS > pkglibdir = $(shell pg_config --pkglibdir) > else > # existing code to set up pkglibdir > endif Tha

Re: [HACKERS] Making pgxs builds work with a relocated installation

2005-09-27 Thread Magnus Hagander
> > > > The other open issue in this area was that on Windows, > > > pg_config needs > > > > to return space-free path names to avoid breaking the > > > makefiles. It > > > > was suggested that this could be handled by passing > > > pg_config's result > > > > path names through GetShortPathName()

Re: [HACKERS] Making pgxs builds work with a relocated installation

2005-09-27 Thread Dave Page
> -Original Message- > From: Magnus Hagander [mailto:[EMAIL PROTECTED] > Sent: 27 September 2005 09:19 > To: Dave Page; Tom Lane; Peter Eisentraut > Cc: pgsql-hackers@postgresql.org > Subject: RE: [HACKERS] Making pgxs builds work with a > relocated instal

Re: [HACKERS] Making pgxs builds work with a relocated installation

2005-09-27 Thread Dave Page
> -Original Message- > From: Magnus Hagander [mailto:[EMAIL PROTECTED] > Sent: 27 September 2005 08:58 > To: Dave Page; Tom Lane; Peter Eisentraut > Cc: pgsql-hackers@postgresql.org > Subject: RE: [HACKERS] Making pgxs builds work with a > relocated installati

Re: [HACKERS] Making pgxs builds work with a relocated installation

2005-09-27 Thread Magnus Hagander
> > The other open issue in this area was that on Windows, > pg_config needs > > to return space-free path names to avoid breaking the > makefiles. It > > was suggested that this could be handled by passing > pg_config's result > > path names through GetShortPathName() on that platform. >

Re: [HACKERS] Making pgxs builds work with a relocated installation

2005-09-27 Thread Dave Page
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane > Sent: 27 September 2005 01:13 > To: Peter Eisentraut > Cc: pgsql-hackers@postgresql.org > Subject: [HACKERS] Making pgxs builds work with a relocated > installa

[HACKERS] Making pgxs builds work with a relocated installation

2005-09-26 Thread Tom Lane
I looked at the recently noted problem that pgxs builds only work if the installation paths recorded in Makefile.global are accurate; which pretty much breaks our claim to supporting relocatable installations. What I propose we do about this is change the path setup section of Makefile.global to l