[petsc-dev] CFLAGS and COPTFLAGS

[Barry Smith]

  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’))

  Or are you referring to make CFLAGS=-O3  ex1 which certainly works but I don’t recommend it?

  Is the problem that though CFLAGS=-O3 should work for configure, there is a bug in configure where it gets ignored? It seems reasonable to me that this should work.

  Barry


On Jan 17, 2014, at 11:48 AM, Jed Brown <jed at jedbrown.org> wrote:

> As far as I know, this is not a widespread convention.  Lots of users
> put in CFLAGS=-O3 and either don't notice that it doesn't get used or
> are frustrated that it's not used.  Is the "auto" value of splitting out
> COPTFLAGS worth this confusion?  Or can we make the behavior more
> obvious?