[petsc-dev] CFLAGS and COPTFLAGS

[Jed Brown]

Barry Smith <bsmith at mcs.anl.gov> writes:

>   I do not understand the context of this email at all.
>
>   Are you referring to putting CFLAGS=-O3 inside a ./configure option?
>   If so I see help.addArgument('Compilers', '-CFLAGS=<string>',
>   nargs.Arg(None, None, 'Specify the C compiler options’))

If you configure with CFLAGS=-O3 --with-debugging=0, configure will test
the -O flag and ultimately use -O3 -O.  The latter takes precedence, so
the -O3 is effectively ignored.  To replace the optimization flag, one
is (currently) supposed to use COPTFLAGS=-O3 --with-debugging=0.  This
is surprising because COPTFLAGS is not a widespread convention.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20140117/245906c3/attachment.sig>