On 10/4/10 6:52 PM, "Dennis Peterson" <denni...@inetnw.com> wrote:
> On 10/4/10 6:25 PM, Al Varnell wrote:
>
>> otool gives me identical results
>>
Sorry, I guess I should have said it's identical to yours:
Load command 9
cmd LC_LOAD_DYLIB
cmdsize 52
name /usr/lib/libbz2.1.0.dylib (offset 24)
time stamp 2 Wed Dec 31 16:00:02 1969
current version 1.0.5
compatibility version 1.0.0
>> I've got a PPC so I'm still at Leopard 10.5.8.
>>
>> $ ls -l *bz2*
>> -rwxr-xr-x 1 root wheel 282048 Nov 11 2008 libbz2.1.0.4.dylib
>> -rwxr-xr-x 1 root wheel 282048 Jun 17 2009 libbz2.1.0.5.dylib
>> lrwxr-xr-x 1 root wheel 18 Apr 4 2010 libbz2.1.0.dylib ->
>> libbz2.1.0.5.dylib
>> lrwxr-xr-x 1 root wheel 18 Apr 4 2010 libbz2.dylib ->
>> libbz2.1.0.5.dylib
>>
>> Could it be that clamd was somehow compiled with 1.0.2?
>
> It appears that your library is 1.0.2 regardless of what the binary might be.
> Did you ever do a restore of you /lib? That's most frequently how libs get
> mysteriously backleveled. Assuming it was ever upgraded to 1.0.5.
>
So again, how come clamd says it loads 1.0.2
Load command 13
cmd LC_LOAD_DYLIB
cmdsize 52
name /usr/lib/libbz2.1.0.dylib (offset 24)
time stamp 2 Wed Dec 31 16:00:02 1969
current version 1.0.2
compatibility version 1.0.0
while bzip2 loads 1.0.5?
-Al-
--
Al Varnell
Mountain View, CA
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
