Re: More SSL crash woes

From: Jeff Amiel <jamiel(at)istreamimaging(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: More SSL crash woes
Date: 2008-04-08 21:56:30
Message-ID: 47FBEA0E.40305@istreamimaging.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane wrote:
> One idea: you are linking to /usr/local/ssl/lib/libssl.so, but is
> it possible that when you compile PG it is finding the header files
> for some other version?
>

yes...if I could figure out how the include path is being set on the
postgresql build.
I'm looking at the config.log and I see no reference to -I (to set the
include path)
It simply references the header files as "openssl/ssl.h"

Any way to tell the default include path for gcc?
There are two sets:

/usr/sfw/include/openssl/ssl.h (older incorrect one)
/usr/local/ssl/include/openssl/ssl.h (newer 'correct one)

I guess I could build something that #includes openssl/ssl.h and
'butcher' the bad one and see what happens.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Manuel Sugawara 2008-04-08 22:06:58 Re: Cannot use a standalone backend to VACUUM in "postgres""
Previous Message Tom Lane 2008-04-08 21:33:10 Re: More SSL crash woes