Dave Isaacs skrev, on 24-10-2007 15:11:

> The target system for my dkim-filter installation is a Red Hat EL4
> system, which includes openssl 0.9.7.
> 
> Since I want support for SHA256, I will have to use openssl 0.9.8 or
> better. I see two options
> 
> (1) Install the latest openssl on the system, in a location separate
> from the existing openssl installation, and compile dkim-filter in such
> a way that it points to the 0.9.8 installation.
> 
> (2) Link dkim-filter statically with openssl 0.9.8, so that I don't have
> to install another instance of openssl on the target system.
> 
> I'd rather not do (1), for reasons of convenience which I will not go
> into right now. 
> 
> That leaves me with option (2). Is it possible to statically link with
> openssl? How would I do this?

There's one more option, that I've done with all my rigs - since RHEL4 
is definitely yesterday's:

3: upgrade/reinstall RHEL5/CentOS5/Fedora FC >= FC6.

Really, RHAS4 is, of date, definitely passé. Much good stuff just 
doesn't work on it any longer - or if it does, simply by botching source 
to /usr/local, you name it.

People making *structural* changes, such as installing upgrades of 
(openssl|Cyrus SASL|Oracle BDB|more stuff) without doing it by using 
good rpms are simply heaping coals upon their heads. Yes, I've many 
years experience, it was all botching.

Best,

--Tonni

-- 
Tony Earnshaw
Email: tonni at hetnet dot nl

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
dkim-milter-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss

Reply via email to