Re: gcc ignoring defined macros?

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Adam H(dot) Pendleton" <fmonkey(at)fmonkey(dot)net>
Cc: "Hiroshi Saito" <saito(at)inetrt(dot)skcapi(dot)co(dot)jp>, <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: gcc ignoring defined macros?
Date: 2003-10-07 07:24:52
Message-ID: 03AF4E498C591348A42FC93DEA9661B83AF283@mail.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

-----Original Message-----
From: Adam H. Pendleton [mailto:fmonkey(at)fmonkey(dot)net]
Sent: 06 October 2003 18:26
To: Dave Page
Cc: Hiroshi Saito; pgadmin-hackers(at)postgresql(dot)org
Subject: Re: [pgadmin-hackers] gcc ignoring defined macros?


Dave Page wrote:

I was about to fix this, when I realized that I was about to
add -DSSL to the command-line for *all* situations. Is this what we
want, or is this supposed to be a conditional compile option? If it's
needed for *all* situations, then why included it at all, why not just
remove the #ifdefs and always compile the SSL code?

We should probably include it as an option as not everyone compiles
PostgreSQL with SSL support (I normally don't for example). Can it be
done automagically by looking for the SSL_connect symbol in
libpq.a/libpq.so?

Regards, Dave.

Browse pgadmin-hackers by date

  From Date Subject
Next Message Jean-Michel POURE 2003-10-07 11:45:41 wxWindows RPMs
Previous Message Dave Page 2003-10-07 07:10:43 Re: Update