With USE="cxx fortran mpi-threads threads -debug -doc -pvfs2 -romio" I get following QA when emergeing sys-cluster/mpich2-1.0.8 from the tree * QA Notice: Unrecognized configure options: * * configure: WARNING: Unrecognized options: --enable-sharedlibs, --with-thread-package, --enable-f77, --enable-f90, --enable-threads, --with-pm, --disable-mpe, --disable-romio, --enable-cxx * configure: WARNING: Unrecognized options: --enable-sharedlibs, --with-thread-package, --enable-f77, --enable-f90, --enable-threads, --with-pm, --disable-mpe, --disable-romio, --enable-cxx * configure: WARNING: Unrecognized options: --enable-sharedlibs, --with-thread-package, --enable-f77, --enable-f90, --enable-threads, --with-pm, --disable-mpe, --disable-romio, --enable-cxx * configure: WARNING: Unrecognized options: --enable-sharedlibs, --with-thread-package, --enable-f77, --enable-f90, --enable-threads, --with-pm, --disable-mpe, --disable-romio, --enable-cxx
This is due to the way that upstream has decided to recursively call configure in various subdirectories. For example, the main mpich2 configure script accepts --enable-cxx, but src/pm/gforker, for example, doesn't. I honestly think it's just cosmetics, but you might be able to convince upstream to accept a patch that correctly strips configure arguments. Closing as UPSTREAM, but thanks for filing the report.
*** Bug 272370 has been marked as a duplicate of this bug. ***