Re: TODO item: make world safe for spaces in build/install - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: TODO item: make world safe for spaces in build/install
Date
Msg-id 200501040513.j045DO807072@candle.pha.pa.us
Whole thread Raw
In response to Re: TODO item: make world safe for spaces in build/install paths  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut wrote:
> Tom Lane wrote:
> > Pursuant to Theodore Petrosky's recent trouble report, I thought I
> > would see what happens if you try to build Postgres in a directory
> > whose path contains spaces,
> 
> The last I heard in the autotools community on this issue was "forget 
> it".  Not that that means it's impossible, but you're going to fight a 
> hard battle with make, which has no quoting mechanism at all.
> 
> > or if the install prefix contains spaces.
> 
> This should be achievable, with a few thousand quotes in the right 
> places.

Interesting.  TODO updated:

* Allow building with directories containing spaces
 There are two capabilities here, first the ability to build from a source directory that contains spaces, and second
theability to install into a directory that contains spaces.  The first is probably not possible because 'gmake' and
othercompiler tools do not fully support spaces in path names.  The second is possible with proper quoting in the
makefiles. Because PostgreSQL supports relocatable installs, it is possible to install into a directory that doesn't
containspaces and then copy the install to a directory with spaces.
 

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: race condition for drop schema cascade?
Next
From: Bruce Momjian
Date:
Subject: Re: [PATCHES] Bgwriter behavior