In this case, should we only display the warning if debug build was
implicit ?
for example, ./configure from git would display the warning (implicit
debug),
but ./configure --enable-debug would not (explicit debug), regardless we
built from git or a tarball
On 3/2/2016 1:13 PM, Jeff Squyres (jsquyres) wrote:
On Mar 1, 2016, at 10:06 PM, Gilles Gouaillardet <gil...@rist.or.jp> wrote:
what about *not* issuing this warning if OpenMPI is built from git ?
that would be friendlier for OMPI developers,
and should basically *not* affect endusers, since they would rather build OMPI
from a tarball.
We're actually specifically trying to catch this case: someone builds from git,
doesn't know (or care) that it's a debug build, and runs some performance tests
with Open MPI.
We figured that it would be sufficient for OMPI devs to set the env variable in
their shell startup files to avoid the message.
