Re: exiscan & spf: the same problem.

On Thu, Aug 19, 2004 at 11:30:50AM +0200, Oliver Eikemeier wrote:
> andy wrote:

> >No, I had the same problem, I can assure you its the make.conf file.

> Yup, I guess that's true. This should affect other ports too.

This box has

mash:/usr/src> pkg_info | wc -l
     362

ports installed. Looks like exim+exiscan+spf is the only port affected.

> >I commented all the #CFLAGS= -O3 -pipe and anything else related to 
> >build.

> You just need to use CFLAGS+= instead. -O3 is likely to cause problems, 
> depending on the gcc version you have.

> >#CPUTYPE=i686
> >#NO_CPU_CFLAGS= true    # Don't add -march=<cpu> to CFLAGS automatically
> >#NO_CPU_COPTFLAGS=true  # Don't add -march=<cpu> to COPTFLAGS 
> >automatically

> >etc etc.

> These are fine. Only CFLAGS is a problem here.

Commenting out CFLAGS in /etc/make.conf do the trick. 

Andy, you were right about make.conf. The point is that I just renamed
make.conf into make.conf.old. But I have WRKDIRPREFIX=/var/tmp in it,
so, when I rebuilt the port, I've checked previous binary, so I didn't
notice any difference.

And great thanks to Oliver for all the time he spent trying to find out
what's happening.

> >If you still cant get it to work, just edit the Makefile in ports dir 
> >and force the build.

> .. this should be investigated further, since it is likely to affect 
> other ports.

BTW, just a wild guess. All this happened on a two-processor box. I
asked another guy who blamed the same problem, if his 'problem box' has
two proccessors too. A minute ago he confirmed this.

Ideas?

Regards,
-- 
	      Apathists of the world... aah, who cares?