Re: Trouble porting postgreSQL to WinNT

Is it that \n in genbki.sh.  Please try to apply this patch to
genbki.sh.in, re-run configure, and try again.  If you want to manually
patch it, the \n in the sed script is wrong.


> =?iso-8859-1?Q?"Felix=20K=F6nig"?= <felix.koenig@web.de> writes:
> > gcc -I../../../include -I../../../backend   -I/usr/local/include -O2 -I/usr/local/inc
> > lude -DBUILDING_DLL=1 -Wall -Wmissing-prototypes -Wmissing-declarations -I../..    -c
> >  -o istrat.o istrat.c
> > istrat.c: In function `OperatorRelationFillScanKeyEntry':
> > istrat.c:494: `F_OIDEQ' undeclared (first use in this function)
> > istrat.c:494: (Each undeclared identifier is reported only once
> > istrat.c:494: for each function it appears in.)
>
> F_OIDEQ (and a lot of other F_xxx macros) should be declared in
> src/backend/fmgr.h, which is normally generated during build by
> the shell script src/backend/utils/Gen_fmgrtab.sh.  I speculate
> that fmgr.h is completely hosed (perhaps empty) due to script
> execution problems, and that this just happens to be the first
> place in the compile that references an F_xxx macro.
>
> Gen_fmgrtab.sh depends on a shell, awk, sed, and a bunch of other
> stuff, so I wouldn't be too surprised if it fails under Win2000.
> Not sure why Sasha is seeing a problem, though, unless he's trying
> to build under Windows ...
>
>             regards, tom lane
>


--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
Index: genbki.sh.in
===================================================================
RCS file: /home/projects/pgsql/cvsroot/pgsql/src/backend/catalog/genbki.sh,v
retrieving revision 1.18
retrieving revision 1.19
diff -c -r1.18 -r1.19
*** genbki.sh    2000/10/28 22:14:14    1.18
--- genbki.sh    2001/01/16 22:48:34    1.19
***************
*** 161,170 ****
  ;g' | # we must run a new sed here to see the newlines we added
  sed -e "s/;[     ]*$//g" \
      -e "s/^[     ]*//" \
!     -e "s/[     ]Oid/\ oid/g" \
!     -e "s/[     ]NameData/\ name/g" \
      -e "s/^Oid/oid/g" \
!     -e "s/^NameData/\name/g" \
      -e "s/(NameData/(name/g" \
      -e "s/(Oid/(oid/g" \
      -e "s/NAMEDATALEN/$NAMEDATALEN/g" \
--- 161,170 ----
  ;g' | # we must run a new sed here to see the newlines we added
  sed -e "s/;[     ]*$//g" \
      -e "s/^[     ]*//" \
!     -e "s/[     ]Oid/ oid/g" \
!     -e "s/[     ]NameData/ name/g" \
      -e "s/^Oid/oid/g" \
!     -e "s/^NameData/name/g" \
      -e "s/(NameData/(name/g" \
      -e "s/(Oid/(oid/g" \
      -e "s/NAMEDATALEN/$NAMEDATALEN/g" \