postgresql-cygwin is working fine. See the testfarm.
Just cygwin itself, cygserver - the IPC daemon - has problems.
On msgctl(IPC_INFO) the internal msg buffer struct msqid_ds *buf is
allocated at a non-writable area, IsBadWritePtr() fails. I suspect it's
a new gcc-3.4 feature, but haven't found
Is Cygwin now working properly in CVS and beta5? I assume so.
---
Magnus Hagander wrote:
> > >>beta4 - cygwin:
> > >>postgres.exe fails to build, because __imp__my_exec_path from
> > >>src/timezone/pgtz.o cannot be resolve
Reini Urban wrote:
> Magnus Hagander schrieb:
> >>beta4 - cygwin:
> >>postgres.exe fails to build, because __imp__my_exec_path from
> >>src/timezone/pgtz.o cannot be resolved. previously it was not
> >>imported.
> >
> > This could be related to the patch that went in last weekend to fix
> > comp
> >>beta4 - cygwin:
> >>postgres.exe fails to build, because __imp__my_exec_path from
> >>src/timezone/pgtz.o cannot be resolved. previously it was not
> >>imported.
> >
> > This could be related to the patch that went in last weekend to fix
> > compiles on Win32. DLLIMPORT was added to the hea
Magnus Hagander schrieb:
beta4 - cygwin:
postgres.exe fails to build, because __imp__my_exec_path from
src/timezone/pgtz.o cannot be resolved. previously it was not
imported.
This could be related to the patch that went in last weekend to fix
compiles on Win32. DLLIMPORT was added to the header.
> beta4 - cygwin:
> postgres.exe fails to build, because __imp__my_exec_path from
> src/timezone/pgtz.o cannot be resolved. previously it was not
> imported.
This could be related to the patch that went in last weekend to fix
compiles on Win32. DLLIMPORT was added to the header. If the Makefile
beta4 - cygwin:
postgres.exe fails to build, because __imp__my_exec_path from
src/timezone/pgtz.o cannot be resolved. previously it was not imported.
dlltool --dllname postgres.exe --output-exp postgres.exp --def postgres.def
gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Wendif-labels
-fno
