I tried building with the options from ClamXav article you referenced below but 
it was no help. Still “Segmentation Fault: 11”.

I have 0.98.6 restored from backup so OK for now. Probably no time to work 
further on this until the weekend.

-- 
Larry Stone
[email protected]
http://www.stonejongleux.com/

> On Apr 29, 2015, at 7:22 PM, Al Varnell <[email protected]> wrote:
> 
> I wouldn’t spend a lot of time on it until we get some confirmation from 
> ClamAV®, but the instructions on the ClamXav site for Bring Your Own Engine 
> <http://www.clamxav.com/docs_byo.html> might help.
> 
> -Al-
> …
...

>>> 
>>> On Wed, Apr 29, 2015 at 01:03PM, Larry Stone wrote:
>>>> 
>>>> Clamd throws a "Segmentation Fault: 11" error when attempting to run it 
>>>> when built on Mac OS X 10.10 Yosemite. This happens with both 0.98.6 and 
>>>> 0.98.7 when built on Yosemite (my version of 0.98.6 built on 10.9 ran fine 
>>>> on 10.10). But I just upgraded my server from 10.9 to 10.10 and with 
>>>> today's relase of 0.98.7, this was my first time attempting to build 
>>>> ClamAV under Yosemite.
>>>> 
>>>> Various articles I've found are pointing to an issue with libtool where 
>>>> 10.10 gets treated as if it's 10.1. This article 
>>>> (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63610) seems to describe the 
>>>> issue but a lot of it is beyond me. I've attempted defining 
>>>> MACOSX_DEPLOYMENT_TARGET=10.9 as described in that article but that didn't 
>>>> make a difference (nor am I seeing anything else defining it to 10.10 so I 
>>>> didn't expect it make a difference).
>>>> 
>>>> ./configure is happy and make generates a lot of warning but no errors. 
>>>> The error only happens when trying to run it.
>>>> 
>>>> Note this is ClamAV, not ClamXav.
>>>> 
>>>> -- Larry Stone
>>>> [email protected]



Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Reply via email to