Re: Trouble porting postgreSQL to WinNT

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: " Felix König " <felix(dot)koenig(at)web(dot)de>
Cc: Sasha Pachev <sasha(at)mysql(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Trouble porting postgreSQL to WinNT
Date: 2001-01-27 06:30:59
Message-ID: 20711.980577059@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

=?iso-8859-1?Q?"Felix=20K=F6nig"?= <felix(dot)koenig(at)web(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2001-01-27 06:47:07 Re: Re: Re: MySQL has transactions
Previous Message Lincoln Yeoh 2001-01-27 06:25:42 Re: Re: MySQL has transactions

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-01-27 06:47:07 Re: Re: Re: MySQL has transactions
Previous Message Lincoln Yeoh 2001-01-27 06:25:42 Re: Re: MySQL has transactions