id	summary	reporter	owner	description	type	status	priority	milestone	component	resolution	keywords	cc
689	Duplicate flags	balaji	balaji	"In MPICH2's top-level configure.in, when arguments such as --enable-strict or --enable-g are passed, the corresponding flags are stored in MPICH2_EXTRA_CFLAGS and not in CFLAGS. When autoconf and confdb macros try out various compiler tests, they are not aware of these previous flags because of which they make incorrect decisions for some things. Finally, when the MPICH2 library is being compiled, when the MPICH2_EXTRA_CFLAGS appear in the compiler flags, the behavior of the compiler does not match what was detected by configure, resulting in errors. This was one of the reasons why --enable-strict didn't work correctly for a long time (signal/sigaction was another reason as well).

This ticket is a reminder that we need to go and clean up the configure script of this issue."	bug	closed	minor	future	mpich2	fixed