Re: [HACKERS] pg_config --pgxs on Win32

2005-10-15 Thread Peter Eisentraut
Martijn van Oosterhout wrote: > I don't see an easy way out. Half the system thinks backslashes are > special and need expansion, the other half thinks forward slashes are > option markers. This is really just a variation on the "space in > filenames" issue in UNIX. pg_config --pgxs is supposed to

Re: [HACKERS] pg_config --pgxs on Win32

2005-10-14 Thread Matt Emmerton
> On 10/14/05, Dave Page wrote: > > Won't help: > > > > Microsoft Windows XP [Version 5.1.2600] > > (C) Copyright 1985-2001 Microsoft Corp. > > > > C:\Documents and Settings\dpage>mkdir c:\foo > > > > C:\Documents and Settings\dpage>cd c:/foo > > The system cannot find the path specified. > > > >

Re: [HACKERS] pg_config --pgxs on Win32

2005-10-14 Thread Dave Page
> -Original Message- > From: Christopher A. Watford [mailto:[EMAIL PROTECTED] > Sent: 14 October 2005 15:58 > To: Dave Page > Cc: Tom Lane; Martijn van Oosterhout; Thomas Hallgren; > pgsql-hackers@postgresql.org > Subject: Re: [HACKERS] pg_config --pgxs on Win32 &

Re: [HACKERS] pg_config --pgxs on Win32

2005-10-14 Thread Christopher A. Watford
On 10/14/05, Dave Page wrote: > Won't help: > > Microsoft Windows XP [Version 5.1.2600] > (C) Copyright 1985-2001 Microsoft Corp. > > C:\Documents and Settings\dpage>mkdir c:\foo > > C:\Documents and Settings\dpage>cd c:/foo > The system cannot find the path specified. > > C:\Documents and Setting

Re: [HACKERS] pg_config --pgxs on Win32

2005-10-14 Thread Dave Page
> -Original Message- > From: Tom Lane [mailto:[EMAIL PROTECTED] > Sent: 13 October 2005 20:41 > To: Dave Page > Cc: Martijn van Oosterhout; Thomas Hallgren; > pgsql-hackers@postgresql.org > Subject: Re: [HACKERS] pg_config --pgxs on Win32 > > "Dave

Re: [HACKERS] pg_config --pgxs on Win32

2005-10-13 Thread Martijn van Oosterhout
On Thu, Oct 13, 2005 at 08:36:39PM +0100, Dave Page wrote: > When we first discussed this I posted a very simple example 'cd /' > which does absolutely nothing unlike 'cd \' or 'cd \\' which work as > expected, quite possibly for the reason you suggest. Although the / > is accepted, I don't believe

Re: [HACKERS] pg_config --pgxs on Win32

2005-10-13 Thread Tom Lane
"Dave Page" writes: > When we first discussed this I posted a very simple example 'cd /' > which does absolutely nothing unlike 'cd \' or 'cd \\' which work as > expected, quite possibly for the reason you suggest. Although the / is > accepted, I don't believe it can be called reliable as it obvio

Re: [HACKERS] pg_config --pgxs on Win32

2005-10-13 Thread Thomas Hallgren
Dave Page wrote: -Original Message- From: Martijn van Oosterhout [mailto:[EMAIL PROTECTED] Sent: Thu 10/13/2005 8:08 PM To: Tom Lane Cc: Thomas Hallgren; Dave Page; pgsql-hackers@postgresql.org Subject: Re: [HACKERS] pg_config --pgxs on Win32 Besides, Windows has accepted the

Re: [HACKERS] pg_config --pgxs on Win32

2005-10-13 Thread Dave Page
-Original Message- From: Martijn van Oosterhout [mailto:[EMAIL PROTECTED] Sent: Thu 10/13/2005 8:08 PM To: Tom Lane Cc: Thomas Hallgren; Dave Page; pgsql-hackers@postgresql.org Subject: Re: [HACKERS] pg_config --pgxs on Win32 > Besides, Windows has accepted the forward slash

Re: [HACKERS] pg_config --pgxs on Win32

2005-10-13 Thread Andrew Dunstan
Dave Page wrote: We should probably document that pg_config may not work reliably with non-mingw tools in that case. Microsoft code may or may not do what is expected with front slashes. BTW Thomas - I thought you said \\ did work when you were testing options for me, or was that just msys

Re: [HACKERS] pg_config --pgxs on Win32

2005-10-13 Thread Martijn van Oosterhout
On Thu, Oct 13, 2005 at 02:53:09PM -0400, Tom Lane wrote: > Thomas Hallgren <[EMAIL PROTECTED]> writes: > > I do have a workaround in place that makes it work for me now. I do > > $(dir $(subst \\,/,xxx)) and that works fine but given that the targeted > > platform for pgxs on Win32 is MinGW, per

Re: [HACKERS] pg_config --pgxs on Win32

2005-10-13 Thread Tom Lane
Thomas Hallgren <[EMAIL PROTECTED]> writes: > I do have a workaround in place that makes it work for me now. I do > $(dir $(subst \\,/,xxx)) and that works fine but given that the targeted > platform for pgxs on Win32 is MinGW, perhaps it should output forward > slashes anyway. I've already app

Re: [HACKERS] pg_config --pgxs on Win32

2005-10-13 Thread Thomas Hallgren
Dave Page wrote: We should probably document that pg_config may not work reliably with non-mingw tools in that case. Microsoft code may or may not do what is expected with front slashes. BTW Thomas - I thought you said \\ did work when you were testing options for me, or was that just msys ra

Re: [HACKERS] pg_config --pgxs on Win32

2005-10-13 Thread Dave Page
-Original Message- From: "Tom Lane"<[EMAIL PROTECTED]> Sent: 13/10/05 18:23:13 To: "Thomas Hallgren"<[EMAIL PROTECTED]> Cc: "pgsql-hackers@postgresql.org" Subject: Re: [HACKERS] pg_config --pgxs on Win32 >> The mingw GNU Make is not too

Re: [HACKERS] pg_config --pgxs on Win32

2005-10-13 Thread Tom Lane
Thomas Hallgren <[EMAIL PROTECTED]> writes: > Something changed very recently in the output from pg_config --pgxs > command on Win32. It now outputs double backslash everywhere instead > of forward slashes. The mingw GNU Make is not too happy about the > double backslashes. I said that was a bad i

[HACKERS] pg_config --pgxs on Win32

2005-10-13 Thread Thomas Hallgren
Something changed very recently in the output from pg_config --pgxs command on Win32. It now outputs double backslash everywhere instead of forward slashes. The mingw GNU Make is not too happy about the double backslashes. I do: export PGXS := $(dir $(shell pg_config --pgxs)) and now it yields