Yes, the Makefiles cannot deal with spaces correctly.
Seems we should avoid use the `complicated' path.
Wes [EMAIL PROTECTED] wrote
System: Mac OS X 10.4.2
PostgreSQL: 8.1 b2
Running 'make check', I get the following failure:
rm -rf ./testtablespace
mkdir ./testtablespace
/bin/sh
On 10/2/05 7:48 AM, William ZHANG [EMAIL PROTECTED] wrote:
Yes, the Makefiles cannot deal with spaces correctly.
Seems we should avoid use the `complicated' path.
Such paths are normal on systems with a GUI interface. They are not out of
the ordinary nor complicated.
Wes
On Sun, Oct 02, 2005 at 12:15:05PM -0500, Wes wrote:
On 10/2/05 7:48 AM, William ZHANG [EMAIL PROTECTED] wrote:
Yes, the Makefiles cannot deal with spaces correctly.
Seems we should avoid use the `complicated' path.
Such paths are normal on systems with a GUI interface. They are not out
Wes [EMAIL PROTECTED] writes:
On 10/2/05 7:48 AM, William ZHANG [EMAIL PROTECTED] wrote:
Yes, the Makefiles cannot deal with spaces correctly.
Seems we should avoid use the `complicated' path.
Such paths are normal on systems with a GUI interface. They are not out of
the ordinary nor
On 10/2/05 4:13 PM, Martijn van Oosterhout kleptog@svana.org wrote:
Problem is, the space is also the word seperator. So if you have a
space seperated list of words (ie normal for make), names with spaces
are a pain.
It occurred to me that you might be able to replace the spaces in the
System: Mac OS X 10.4.2
PostgreSQL: 8.1 b2
Running 'make check', I get the following failure:
rm -rf ./testtablespace
mkdir ./testtablespace
/bin/sh ./pg_regress --temp-install --top-builddir=../../..
--temp-port=55432 --schedule=./parallel_schedule --multibyte=SQL_ASCII
--load-language=plpgsql
