Let me rephrase that.
i will set the parameter in the etc/openmpi-mca-params.conf of my
install directory,
and i will very likely forget about it (etc/openmpi-mca-params.conf is
not overwritten by make install, right ?)
if one day, i decide to configure without --enable-debug and run a
performance benchmark, then i will not get the warning i need (and yes,
i will be the only one to blame ... but isn't it something we want to
avoid here ?)
Cheers,
Gilles
On 3/2/2016 1:43 PM, George Bosilca wrote:
On Mar 1, 2016, at 22:27 , Gilles Gouaillardet <gil...@rist.or.jp> wrote:
be "me-friendly" :-)
i explicitly configure with --enable-debug --enable-picky from git, so i
(hopefully) know what i am doing and do not want any warning.
iirc, cisco mtt does that too, and i am not sure you would want a warning
and/or update your mtt config.
this is not a strong opinion, and i am fine with setting a parameter (i will
likely soon forget i set that) in a config file.
And you will be painfully reminded about that ;)
The emitted message was supposed to contain the MCA parameter that need to be
set to silence the warning.
George.
Cheers,
Gilles
On 3/2/2016 1:21 PM, Jeff Squyres (jsquyres) wrote:
On Mar 1, 2016, at 10:17 PM, Gilles Gouaillardet <gil...@rist.or.jp> wrote:
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
We don't currently distinguish between these two cases.
What is the rationale for only warning on implicit debug builds?
_______________________________________________
devel mailing list
de...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
Link to this post:
http://www.open-mpi.org/community/lists/devel/2016/03/18656.php
_______________________________________________
devel mailing list
de...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
Link to this post:
http://www.open-mpi.org/community/lists/devel/2016/03/18658.php
