Rishi Sharma <rsharma@Bigstep.net> wrote:
>
> Just a little more info for you:
>
[...]
> make[3]: Entering directory `/usr/src/postgresql-7.1.2/src/backend/utils'
> CPP='gcc -E' AWK='gawk' /bin/sh.exe Gen_fmgrtab.sh
> ../../../src/include/catalog/
> pg_proc.h
> -nThe system cannot find the file specified.
> cpp0.exe: output pipe has been closed
> Gen_fmgrtab.sh failed
[...]
>
> where is fmgroids.h?
It's obvious that it hasn't been created, as far as the script used to generate it failed. Maybe your cygwin
environmentisn't properly configured?
> -----Original Message-----
[...]
You should decide to use a single notation for cygwin paths in your scripts -- either the windowish way, addapted to
un*xports, e.g. c:/cygwin/usr/bin, or the un*x way, /usr/bin. In a hybrid environment as your IIS & postgresql/perl
lookslike, it's a good thing to initialize the PATH environment variable with a value to satisfy both the win32 and the
cygwinapps. A good test would be to try the printenv or test-cgi scripts from apache distribution, adapted to your IIS.
A specific advice would be to put #!c:/cygwin/local/bin/perl instead #!/usr/local/bin/perl at the begining of your
scripts-- although your IIS knows to do a c:\cygwin\local\bin\perl.exe on the *.cgi files.
Also if your scripts are in perl, you need the Pg.dll library, which builds OOTB for PostgreSQL'n'perl/cygwin.
SLao
__________________________________________________________________
Get your own FREE, personal Netscape Webmail account today at http://webmail.netscape.com/
