Re: Runtime Problems

Hi Andrew

if I try to just run bin/initdb in the pgsql directory I get the normal
error
that bin is not an executable. If I try the full path c:\pgsql\bin\initdb I
get the same old error.

Regards

Richard

-----Original Message-----
From: Andrew Dunstan [mailto:andrew(at)dunslane(dot)net]
Sent: Monday, 17 May 2004 9:42 AM
To: Richard Luckhurst
Cc: PGSQL Hackers
Subject: Re: [pgsql-hackers-win32] Runtime Problems

Richard Luckhurst wrote:

>Hi Andrew
>
>I ran configure with the --without-zlib option
>

What happens if you cd to c:\pgsql and run

bin/initdb -D c:\pgsql\data -W --lc-collate=C

?

cheers

andrew

>
>Regards
>
>Richard
>
>-----Original Message-----
>From: pgsql-hackers-win32-owner(at)postgresql(dot)org
>[mailto:pgsql-hackers-win32-owner(at)postgresql(dot)org]On Behalf Of Andrew
>Dunstan
>Sent: Sunday, 16 May 2004 8:13 PM
>To: pgsql-hackers-win32(at)postgresql(dot)org
>Subject: Re: [pgsql-hackers-win32] Runtime Problems
>
>
>Richard Luckhurst said:
>
>
>>Hi All
>>
>>I have just recompiled using the latest snapshot and I am still getting
>>exactly the same errors. I still have the compile stuff in msys and the
>>copy in c:\pgsql so that explains why it is picking it up twice I
>>guess. In any case I still have the error I first asked about last
>>week.
>>
>>
>
>What parameters did you run configure with?
>
>cheers
>
>andrew
>
>
>
>
>>Regards
>>
>>Richard
>>
>>-----Original Message-----
>>From: pgsql-hackers-win32-owner(at)postgresql(dot)org
>>[mailto:pgsql-hackers-win32-owner(at)postgresql(dot)org]On Behalf Of Andrew
>>Dunstan
>>Sent: Thursday, 13 May 2004 8:54 PM
>>To: pgsql-hackers-win32(at)postgresql(dot)org
>>Subject: Re: [pgsql-hackers-win32] Runtime Problems
>>
>>
>>I said:
>>
>>
>>>Richard Luckhurst said:
>>>
>>>
>>>>Hello All
>>>>
>>>>I am quite new to pgsql and the Win32 port. I have just tried
>>>>Vishal's new guide to building
>>>>and I am having what looks like a path problem when I try to
>>>>initialise a database. I am using
>>>>Windows 2000. Everything builds and installs OK and I have copied the
>>>>files in the msys\1.0\local\pgsql
>>>>to my c:\pgsql folder as per the instructions. I have added
>>>>C:\pgsql\bin and c:\pgsql\lib to my path
>>>>as instructed. When I try to run initdb I get the following error
>>>>
>>>>initdb -D c:\pgsql\data -W --lc-collate=C
>>>>
>>>>
>>The clue is actually in these following 4 lines
>>
>>
>>
>>>>Bad command or file name
>>>>fgets failure: No error
>>>>Bad command or file name
>>>>fgets failure: No error
>>>>
>>>>
>>For some reason, initdb has found postgres.exe in 2 locations but in
>>both cases has been unable to execute it, and consequently unable to
>>read in the version string.
>>
>>That's a bit strange - I have no explanation for it right now.
>>
>>The relevant code has just been refactored by Bruce as part of the
>>relocation stuff.
>>
>>For now, I still recommend running from the installed path.
>>
>>cheers
>>
>>andrew
>>
>>
>>
>>
>>>>The program "postgres" is needed by initdb but was not found in the
>>>>directory "C:/msys/1.0/local/pgsql/bin". Check your installation
>>>>
>>>>I would appreciate any clues here as this has me stumped. I don't
>>>>understand why is should even be looking in the msys directory.
>>>>
>>>>
>>>>
>>>I haven't had time to read the document referred to, but if it
>>>currently recommends that you run from anywhere but the installed path
>>>then I disagree with it. When we get relocatable installs, which Bruce
>>>is working on, you will be able to move the whole installation around
>>>to your heart's content.
>>>
>>>Have you checked that there is still in fact a
>>>C:/msys/1.0/local/pgsql/bin/postgres.exe? Could it be a permissions
>>>problem?
>>>
>>>
>>>
>>
>>
>
>
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
>
>
>__________ NOD32 1.762 (20040516) Information __________
>
>This message was checked by NOD32 antivirus system.
>http://www.nod32.com
>
>
>
>

__________ NOD32 1.762 (20040516) Information __________

This message was checked by NOD32 antivirus system.
http://www.nod32.com