Milter-greylist

From the Changelog:
1.3.4:
        DNS support in greylist.conf through the domain keyword
        Make the greylist timeout a config file option

The other desirable features will take some time to implement, so I
think 1.3.4 could be a good candidate for the new 1.4 stable branch.

Test time has come. I need you there: milter-greylist has grown quite
feature-rich and it's not easy to test that everything is alright.

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

manu@... wrote:

> 
> Test time has come. I need you there: milter-greylist has grown quite
> feature-rich and it's not easy to test that everything is alright.

This is a small patch that I need to build milter-greylist really out of 
the box on my Solaris machines, where 'cc' is Sun's compiler and gcc is 
called gcc.

-- 
Matthieu Herrb

On Thu, May 27, 2004 at 03:30:48PM +0200, Matthieu Herrb wrote:
> This is a small patch that I need to build milter-greylist really out of 
> the box on my Solaris machines, where 'cc' is Sun's compiler and gcc is 
> called gcc.

There is no reason why it should not build with Solaris' cc. What error
do you have?

-- 
Emmanuel Dreyfus
manu@...

Emmanuel Dreyfus wrote:
> On Thu, May 27, 2004 at 03:30:48PM +0200, Matthieu Herrb wrote:
> 
>>This is a small patch that I need to build milter-greylist really out of 
>>the box on my Solaris machines, where 'cc' is Sun's compiler and gcc is 
>>called gcc.
> 
> 
> There is no reason why it should not build with Solaris' cc. What error
> do you have?
>
It builds find, but Makefile.in hardcodes -Wall -O2 into CFLAGS. Since 
I'm too lazy for now to fix your configure.in script to only set those 
options if $CC is really gcc, I've just changed Makefile.in so that the 
resulting Makefile uses whatever $CC was found by configure.
-- 
Matthieu Herrb

Matthieu Herrb <matthieu.herrb@...> wrote:

> It builds find, but Makefile.in hardcodes -Wall -O2 into CFLAGS. Since
> I'm too lazy for now to fix your configure.in script to only set those
> options if $CC is really gcc, I've just changed Makefile.in so that the
> resulting Makefile uses whatever $CC was found by configure.

What option bugs Solaris' cc? -Wall or -O2?

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

Cyril Guibourg <cg+milter-greylist@...> wrote:

> > What option bugs Solaris' cc? -Wall or -O2? 
> I would bet for -Wall :)

Yes, -O2 is added in @CC@ automatically anyway, so we can drop it. I'll
test for -Wall availability.

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

manu@... writes:

> What option bugs Solaris' cc? -Wall or -O2?

I would bet for -Wall :)

On 27 May 2004, at 20:50, manu@... wrote:

> Matthieu Herrb <matthieu.herrb@...> wrote:
>
>> It builds find, but Makefile.in hardcodes -Wall -O2 into CFLAGS. Since
>> I'm too lazy for now to fix your configure.in script to only set those
>> options if $CC is really gcc, I've just changed Makefile.in so that 
>> the
>> resulting Makefile uses whatever $CC was found by configure.
>
> What option bugs Solaris' cc? -Wall or -O2?
>
Both of them. It only accepts -O for optimization, and doesn't know 
anything about the -W options.

-- 
Matthieu

On Thu, May 27, 2004 at 08:50:39PM +0200, Emmanuel Dreyfus wrote:
> What option bugs Solaris' cc? -Wall or -O2?

Both. "-Wall" is "-v", "-O2" is "-xO2". But Solaris C compile will accept
"-O" just fine.

	Kind regards

-- 
Matthias Scheler                                  http://scheler.de/~matthias/