Re: [HACKERS] Compile failure with SSL

2004-06-25 Thread Tom Lane
"Dave Page" <[EMAIL PROTECTED]> writes: > OK, looks like the error below is a Win32 thing. The patch attached > #ifdef'd out the permissions check on the private key file as it won't > work under Windows anyway (a similar check in postmaster.c has has > already been ifdef'd out for the same reason)

Re: [HACKERS] Compile failure with SSL

2004-06-22 Thread Dave Page
> -Original Message- > From: Merlin Moncure [mailto:[EMAIL PROTECTED] > Sent: 21 June 2004 15:40 > To: Dave Page > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: RE: [HACKERS] Compile failure with SSL > > I had made the same changes as you to be_secure...

Re: [HACKERS] Compile failure with SSL

2004-06-21 Thread Merlin Moncure
Dave Page wrote: > OK, looks like the error below is a Win32 thing. The patch attached > #ifdef'd out the permissions check on the private key file as it won't > work under Windows anyway (a similar check in postmaster.c has has > already been ifdef'd out for the same reason). > > Incidently, the

Re: [HACKERS] Compile failure with SSL

2004-06-20 Thread Dave Page
19 June 2004 23:24 > To: [EMAIL PROTECTED] > Subject: [HACKERS] Compile failure with SSL > > I think this is another on of those 'might be Win32 specific' > problems. > When building on XP, with OpenSSL 0.9.7c (from the bitWalk > MinGW tools), I get the follow

[HACKERS] Compile failure with SSL

2004-06-19 Thread Dave Page
I think this is another on of those 'might be Win32 specific' problems. When building on XP, with OpenSSL 0.9.7c (from the bitWalk MinGW tools), I get the following failure: gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -I../../../src/include -I./src/include/port/w