It's not often that I struggle with a problem for this long, find no answers, submit the question to a list and then

EUREKA!

Find the answer elsewhere on the 'net!

Made the changes and I am BACK IN BUSINESS!

Here it is folks, for those of you who have been struggling with the same problem,

http:[EMAIL PROTECTED]/msg04283.html

Re: DBD::Pg
----------------------------------------------------------------------- -

* To: Charles Albrecht <[EMAIL PROTECTED]>, Perl List <[EMAIL PROTECTED]>
* Subject: Re: DBD::Pg
* From: Randall Perry <[EMAIL PROTECTED]>
* Date: Mon, 09 Dec 2002 11:32:41 -0500
* Delivered-to: mailing list [EMAIL PROTECTED]
* In-reply-to: <[EMAIL PROTECTED]>
* Mailing-list: contact [EMAIL PROTECTED]; run by ezmlm
* User-agent: Microsoft-Entourage/10.1.0.2006

----------------------------------------------------------------------- -


Just thought I'd tell you what I discovered. You don't have to sacrifice
PostgreSQL SSL support to use DBD::Pg. Just do the following (also works for
Pg module):

> setenv POSTGRES_LIB "/usr/local/pgsql/lib"
>
> to
>
> setenv POSTGRES_LIB "/usr/local/pgsql/lib -lssl'
>
> so the trick is to include the flag -lssl during the dbd build.



> On Mon, Sep 23, 2002 at 12:59:19PM +0100, Vincent D Murphy wrote:
>>
>> i have omitted the remainder of the output, it just says that the other
>> tests are skipped.
>>
>> i presume this those symbols are the names of C functions, and that
>> this a problem with XS code somewhere. but why the hell would a DBD
>> driver be interested in SSL?
>>
>> i am hoping somebody else has followed this road less travelled [0] [1]
>> with more success and can help me.
>>
>> 0. http:[EMAIL PROTECTED]/index.html#03128
>> 1. http://david.wheeler.net/osx.html
>
> I recompiled PostgreSQL without SSL (TLS) and then DBD::Pg compiled fine
> for me.
>
> -Charles Albrecht
> [EMAIL PROTECTED]

--
Randall Perry
sysTame


Reply via email to