Re: CFLAGS

2004-11-02 Thread David Brodbeck 
On Mon, 1 Nov 2004 14:20:35 -0500, Michael Barnes wrote
> I was able to change the default CFLAGS by putting the CCFLAGS and 
> the CFLAGS values in my environment before running "perl Makefile.PL".
> 
> I would guess that this could be considered a bug, because its not 
> too uncommon for default CFLAGS to be changed during a compilation.

You were right.  It has to go in the environment.

In other words, this doesn't work:

# perl Makefile.PL CCFLAGS="-O"
# make

But this does:

# perl Makefile.PL
# CFLAGS="-O" make

Re: CFLAGS

2004-11-01 Thread David Brodbeck 
On Mon, 01 Nov 2004 11:54:50 -0800, Justin Mason wrote
> BTW the default CFLAGS are coming from whatever perl was built with;
> so I'd be worried about bugs in your perl accordingly ;)

That's not where spamc is getting them.  They're hard-coded in the configure 
script:

ringbill# grep 'O2' -B1 spamc/configure
  if test "$GCC" = yes; then
CFLAGS="-g -O2"
--
  if test "$GCC" = yes; then
CFLAGS="-O2"

Re: CFLAGS

2004-11-01 Thread Justin Mason 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Michael Barnes writes:
> On Mon, Nov 01, 2004 at 12:24:27PM -0500, David Brodbeck wrote:
> > On Wed, 22 Sep 2004 09:15:48 -0700, Justin Mason wrote
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA1
> > > 
> > > David Brodbeck writes:
> > > > Is there a way to get the SpamAssassin build process to use
> > > > -O instead of -O2 while building spamc?  I run FreeBSD on a
> > > > DEC Alpha, and -O2 triggers optimizer bugs in gcc on that
> > > > architecture.  I've just been editing the configure script before
> > > > building, but it'd be nice if there was an easier way.
> > > 
> > > yep:
> > > 
> > > perl Makefile.PL CCFLAGS="-O"
> > 
> > Hmm...just tried that with SpamAssassin 3.0.1 and it *still* built
> > spamc with -O2.  I had to edit spamc/configure again to force it to
> > use -O.
> 
> I was able to change the default CFLAGS by putting the CCFLAGS and the
> CFLAGS values in my environment before running "perl Makefile.PL".
> 
> I would guess that this could be considered a bug, because its not too
> uncommon for default CFLAGS to be changed during a compilation.

BTW the default CFLAGS are coming from whatever perl was built with;
so I'd be worried about bugs in your perl accordingly ;)

you can also do

perl Makefile.PL CCFLAGS="-O"

and that should work.  if it doesn't, it's a bug, because that's pretty
much std perl practice for CPAN modules afaik.

- --j.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh CVS

iD8DBQFBhpSKMJF5cimLx9ARAhTYAJ4tS5ztgAOj5ZcfsmKcKF5o+qDyRQCeJu6C
JCnXNBYqyXv24LuRtKyrtQY=
=l790
-END PGP SIGNATURE-

Re: CFLAGS

2004-11-01 Thread Michael Barnes 
On Mon, Nov 01, 2004 at 12:24:27PM -0500, David Brodbeck wrote:
> On Wed, 22 Sep 2004 09:15:48 -0700, Justin Mason wrote
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> > 
> > David Brodbeck writes:
> > > Is there a way to get the SpamAssassin build process to use
> > > -O instead of -O2 while building spamc?  I run FreeBSD on a
> > > DEC Alpha, and -O2 triggers optimizer bugs in gcc on that
> > > architecture.  I've just been editing the configure script before
> > > building, but it'd be nice if there was an easier way.
> > 
> > yep:
> > 
> > perl Makefile.PL CCFLAGS="-O"
> 
> Hmm...just tried that with SpamAssassin 3.0.1 and it *still* built
> spamc with -O2.  I had to edit spamc/configure again to force it to
> use -O.

I was able to change the default CFLAGS by putting the CCFLAGS and the
CFLAGS values in my environment before running "perl Makefile.PL".

I would guess that this could be considered a bug, because its not too
uncommon for default CFLAGS to be changed during a compilation.

Mike

-- 
/-\
| Michael Barnes <[EMAIL PROTECTED]> |
| UNIX Systems Administrator  |
| College of William and Mary |
| Phone: (757) 879-3930   |
\-/

Re: CFLAGS

2004-11-01 Thread David Brodbeck 
On Wed, 22 Sep 2004 09:15:48 -0700, Justin Mason wrote
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> David Brodbeck writes:
> > Is there a way to get the SpamAssassin build process to use -O instead of 
> > -O2
> > while building spamc?  I run FreeBSD on a DEC Alpha, and -O2 triggers
> > optimizer bugs in gcc on that architecture.  I've just been editing the
> > configure script before building, but it'd be nice if there was an easier 
> > way.
> 
> yep:
> 
> perl Makefile.PL CCFLAGS="-O"

Hmm...just tried that with SpamAssassin 3.0.1 and it *still* built spamc with
-O2.  I had to edit spamc/configure again to force it to use -O.

Should I file this as a bug?

Re: CFLAGS

2004-09-22 Thread Justin Mason 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


David Brodbeck writes:
> Is there a way to get the SpamAssassin build process to use -O instead of -O2
> while building spamc?  I run FreeBSD on a DEC Alpha, and -O2 triggers
> optimizer bugs in gcc on that architecture.  I've just been editing the
> configure script before building, but it'd be nice if there was an easier way.

yep:

perl Makefile.PL CCFLAGS="-O"

- --j.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh CVS

iD8DBQFBUaU0QTcbUG5Y7woRAhOhAJ4ogk1T+VycjtCXbQ7UrFrFXrTgDwCg5gmm
x7/l4PTefoF22qNUJkFBv1M=
=SHCi
-END PGP SIGNATURE-

CFLAGS

2004-09-22 Thread David Brodbeck 
Is there a way to get the SpamAssassin build process to use -O instead of -O2
while building spamc?  I run FreeBSD on a DEC Alpha, and -O2 triggers
optimizer bugs in gcc on that architecture.  I've just been editing the
configure script before building, but it'd be nice if there was an easier way.