<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.0.7">
</HEAD>
<BODY>
Did you use /usr/sbin/Sophos.install to install Sophos?<BR>
<BR>
I posted a response to a similar problem on the faq-o-matic yesterday.<BR>
<BR>
Try using Julian's script to install Sophos.<BR>
<BR>
Steve<BR>
<A HREF="mailto:Steve@Swaney.com">Steve@Swaney.com</A><BR>
<BR>
On Thu, 2003-07-17 at 13:47, Kevin Spicer wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE><FONT COLOR="#737373"><I>Sorry, I meant to post this to the list...
> From: Kevin Spicer <kevins@bmrb.co.uk>
> To: tyler@beloit.edu
> Subject: Re: Sophos issue?
> Date: 17 Jul 2003 18:39:41 +0100
>
> I don't quite understand this step. I am running on an
> AIX5.1 system. I don't have any libsavi.so* files laying
> around anywhere. Should I? Should I skip this step? Am I
> missing libraries that I should have from Sophos? Note: the
> sophos/lib directory has libsavi.a and vdl.* files. Can
> someone clarify this step better to me? -thanks!
>
> You can't skip the step, however it doesn't look good as a .a file is a
> static library, not a shared library like a .so file. So it looks like
> Sophos on AIX is statically linked.
>
> Maybe you could build the savi module statically linked - but this means
> you'll have to rebuild it every time you do an upgrade of Sophos to the
> latest version, you may well decide that isn't worth it.
BMRB International</FONT>
<A HREF="http://www.bmrb.co.uk"><U>http://www.bmrb.co.uk</U></A>
<FONT COLOR="#737373">+44 (0)20 8566 5000
_________________________________________________________________
This message (and any attachment) is intended only for the
recipient and may contain confidential and/or privileged
material. If you have received this in error, please contact the
sender and delete this message immediately. Disclosure, copying
or other action taken in respect of this email or in
reliance on it is prohibited. BMRB International Limited
accepts no liability in relation to any personal emails, or
content of any email which does not directly relate to our
business.</I></FONT></PRE>
</BLOCKQUOTE>
</BODY>
</HTML>