Not exactly - see below
On Oct 6, 2008, at 11:56 AM, Jeff Squyres wrote:
I think the real issue here is that --enable-debug (or the presence
of the .svn or .hg directories) *implies* several other options,
such as --enable-visibility and --enable-memchecker.
As I understand it: the user
I think the real issue here is that --enable-debug (or the presence of
the .svn or .hg directories) *implies* several other options, such as
--enable-visibility and --enable-memchecker.
As I understand it: the user has *not* specifically asked for --enable-
visibility, but is getting a
Hello,
if you allow me my 2 cents:
At configure time, it is possible to distinguish between several
different user inputs:
- the user typed --enable-foo,
- the user typed --disable-foo or --enable-foo=no,
- the user typed --enable-foo=ARG (ARG is available for further
inspection),
- the user
On Oct 3, 2008, at 9:26 AM, Ralph Castain wrote:
However, what about memchecker? Per my earlier note that crossed
this one, is the current behavior a "bug"?
As I said if one request the memchecker and we cannot satisfy it, then
we should exit with a big error message that clearly state
Ah! I was unaware of that behavior for visibility. Thanks for
clarifying - that's a behavior I can live with.
However, what about memchecker? Per my earlier note that crossed this
one, is the current behavior a "bug"?
On Oct 3, 2008, at 7:18 AM, George Bosilca wrote:
Ralph in order to
Ralph in order to have the behavior you describe for the visibility
feature just don't specify --enable-visibility. This will enable it if
the feature is supported and disable (plus a small warning) if not.
We decided a while ago that 1) we should have a consistent behavior
for similar
On Oct 3, 2008, at 1:59 AM, Aurélien Bouteiller wrote:
Hi Ralph,
1. No. Having visibility turned off without knowing it is the best
way for us to commit bugs in the trunk without noticing, I mean
before somebody else get the leg caught in the "not-compiling-trunk
trap". I had more of my
Hi Ralph,
1. No. Having visibility turned off without knowing it is the best way
for us to commit bugs in the trunk without noticing, I mean before
somebody else get the leg caught in the "not-compiling-trunk trap". I
had more of my share of responsibility for that kind of problems in
