was getting confused with the recent addition of "-lutil" to get the
system-level libutil (i.e., Libtool was confusing the two and doing
Bad Things).
This commit was SVN r5467.
Ralf W (core libtool developer). There are still a few more to plug
in ompi_info (mainly concerned with shutting down OMPI/ORTE
subsystems), but they can wait...
This commit was SVN r5466.
we are part of the source tree and not defined otherwise, we are going
with an always defined if ompi_config.h is included policy. If
ompi_config.h is included before mpi.h or before OMPI_BUILDING is set,
it will set OMPI_BUILDING to 1 and enable all the internal code that
is in ompi_config_bottom.h. Otherwise, it will only include the
system configuration data (enough for defining the C and C++ interfaces
to MPI, but not perturbing the user environment).
This should fix the problems with bool and the like that the Eclipse
folks were seeing. It also cleans up some build system hacks that
we had along the way.
Also, don't use int64_t as the default size of MPI_Offset, because it
requires us including stdint.h in mpi.h, which is something we really
shouldn't be doing.
And finally, fix a ROMIO Makefile that didn't set -DOMPI_BUILDING=1,
as ROMIO includes mpi.h, but not ompi_config.h
This commit was SVN r5430.
Comment out pipes stuff for windows. need to come back and fix this properly in the future.
-his line, and those below, will be ignored--
M iof_base_setup.c
This commit was SVN r5424.
* Update cmpset test to call memory barrier when needed before checking the
results
* remove unneeded sync from cmpset_32 on Power PC
This commit was SVN r5420.
- argv[0] should be the name of the executable for the spawned processes.
- if we free a dynamic communicator (instead of disconnecting),
the counter for dynamic communicators has to be decreased as well,
else we core in finalize.
This commit was SVN r5419.
- Print error messages with the basename(argv[0]) rather than
hard-coded argv[0] so that you can see an error message beginning
with "mpirun" when you run mpirun, etc.
- For all processes that died due to a signal:
- If the signal was not SIGKILL, display the first N of them (where
N defaults to 1)
- If more than N processes died due to a non-SIGKILL signal, print
"And X more processes aborted..." kind of message
- Add --aborted command line parameter to change the default value
of N
- Also print out the total number of processes that died due to
SIGKILL, with a disclaimer that it's impossible to know if we
killed them or someone else killed them
This commit was SVN r5406.
