On Mon, Feb 6, 2012 at 8:39 PM, Reynolds, David C.
wrote:
> I've recently installed .97.3 on an SGI Origin 3000 running TRIX v6.5.28
> using gcc 3.2.1. (I did need to make some source file modifications). I was
> able to run clamscan against a directory seemingly without error.
>
> However, I
On Mon, 2012-02-06 at 11:39 -0800, Reynolds, David C. wrote:
> I've recently installed .97.3 on an SGI Origin 3000 running TRIX
> v6.5.28 using gcc 3.2.1. (I did need to make some source file
> modifications). I was able to run clamscan against a directory
> seemingly without error.
>
> However
On Mon, 6 Feb 2012 11:39:32 -0800 Reynolds, David C.
wrote:
> I've recently installed .97.3 on an SGI Origin 3000 running TRIX v6.5.28
> using gcc 3.2.1. (I did need to make some source file modifications). I was
> able to run clamscan against a directory seemingly without error.
>
> However
On 02/06/2012 09:39 PM, Reynolds, David C. wrote:
> I've recently installed .97.3 on an SGI Origin 3000 running TRIX v6.5.28
> using gcc 3.2.1.
Thats a weird version number. GCC 3.3, 3.4 was working I think, I don't think I
ever used gcc 3.2.1, it might be buggy or might not be.
> (I did need t
I've recently installed .97.3 on an SGI Origin 3000 running TRIX v6.5.28 using
gcc 3.2.1. (I did need to make some source file modifications). I was able to
run clamscan against a directory seemingly without error.
However, I would like to run some tests which would indicate catching an
infe