Ok, I've changed some char[] declarations to unsigned char[]; gcc gives
me no warnings with -Wall, but I'm not sure that doesn't mean it's all
fine now.
Also, thanks a lot for the per-user install instructions -- I've added
them to the README.
C
On Fri, 2002-02-22 at 12:54, Erik B. Berry wrote:
Craig Hughes wrote:
> Sorry about that, I used to be much better about not using // and only
> /**/, precisely for cc compatibility. I'll go through and fix all the
This seems fixed in the latest CVS now. There are some unrelated
compilation warnings, in case they are worth fixing:
cc -O sp
On Sun, Feb 17, 2002 at 11:22:56AM -0800, Craig Hughes wrote:
| On Sat, 2002-02-16 at 17:21, Erik B. Berry wrote:
| > I've managed to make/compile the 2.01 release under SunOS 5.7,
| > after changing the compiler to gcc from cc (cc doesn't like C++ //
| > comments in C files).
|
| Sorry about that
Sorry about that, I used to be much better about not using // and only
/**/, precisely for cc compatibility. I'll go through and fix all the
//'s
For personal installations, the Makefile should be able to read an
environment variable called PREFIX and install there. I think you'll
need to hand-
I've managed to make/compile the 2.01 release under SunOS 5.7, after
changing the compiler to gcc from cc (cc doesn't like C++ // comments in C
files). Now, what is the recommended way to begin using SpamAssassin for
my personal account only without a "make install", since that requires
root pr
