Re: [HACKERS] 7.3 Beta 1 Build Error on Cygwin

Seems to build cleanly here now. Perhaps anoncvs just hadn't sync'd up
when you tried Jason?

Regards, Dave.

> -----Original Message-----
> From: Jason Tishler [mailto:jason(at)tishler(dot)net]
> Sent: 05 September 2002 20:38
> To: Peter Eisentraut
> Cc: Bruce Momjian; Dave Page; pgsql-hackers; pgsql-cygwin
> Subject: Re: [HACKERS] 7.3 Beta 1 Build Error on Cygwin
>
>
> Peter,
>
> On Thu, Sep 05, 2002 at 02:51:31PM -0400, Bruce Momjian wrote:
> > Jason Tishler wrote:
> > > On Thu, Sep 05, 2002 at 08:33:20PM +0200, Peter Eisentraut wrote:
> > > > Should all be fixed now.
> > >
> > > Huh? I don't see any recent CVS commits to indicate this.
> >
> > I see as a commit:
> >
> > [snip]
> >
> > I assume it was in there.
>
> Sorry for the noise, but at the time:
>
> cvs status include/miscadmin.h makefiles/Makefile.win
>
> did *not* indicate any recent commits. Maybe you sent the
> above email before you committed your changes?
>
> Anyway, I just tried a:
>
> make distclean
> rm include/miscadmin.h makefiles/Makefile.win # remove my patch
> cvs update
> make
>
> and got the following error:
>
> [snip]
> make[3]: Leaving directory `/home/jt/src/pgsql/src/backend/utils'
> dlltool --dllname postgres.exe --output-exp postgres.exp
> --def postgres.def
> gcc -L/usr/local/lib -o postgres.exe
> -Wl,--base-file,postgres.base postgres.exp access/SUBSYS.o
> bootstrap/SUBSYS.o catalog/SUBSYS.o parser/SUBSYS.o
> commands/SUBSYS.o executor/SUBSYS.o lib/SUBSYS.o
> libpq/SUBSYS.o main/SUBSYS.o nodes/SUBSYS.o
> optimizer/SUBSYS.o port/SUBSYS.o postmaster/SUBSYS.o
> regex/SUBSYS.o rewrite/SUBSYS.o storage/SUBSYS.o
> tcop/SUBSYS.o utils/SUBSYS.o
> libpq/SUBSYS.o(.text+0x1c84):crypt.c: undefined reference
> to `crypt'
> port/SUBSYS.o(.text+0x262):pg_sema.c: undefined reference
> to `semget'
> [snip]
>
> I can get postgres.exe to successfully link by manually
> appending "-lcrypt -lcygipc" to the end of the above gcc command line.
>
> Since you are already working on this, would you be willing
> to fix this problem?
>
> Thanks,
> Jason
>