doesn't do what it was designed for, and therefore wasn't useful, so
per discussion with Ralph last night, we decided to scrap it.
This commit was SVN r2539.
This also includes a checkpoint update to openmpi.c and ompid.c. I have re-enabled the ompid compile.
This latter raises an important point. The trunk compiles the programs like ompid just fine under Linux. It also does just fine for OSX under the dynamic libraries. However, we are seeing errors when compiling under OSX for the static case - the linker seems to have trouble resolving some variable names, even though linker diagnostics show the variables as being defined. Thus, a warning to Mac users that you may have to locally turn things off if you are trying to do static compiles. We ask, however, that you don't commit those changes that turn things off for everyone else - instead, let's try to figure out why the static compile is having a problem, and let everyone else continue to work.
Thanks
Ralph
This commit was SVN r2534.
-- Make code compatiable with expanded libelan interface to free cmdq.
-- Put the pure device_open() related code into a static routine,
to be replaced with provided elan_int().
This commit was SVN r2533.
pcm for RMS:
- support setting vpids from an offset, in case that's what the ns
gave us (ie, not starting from 0)
- if we have it, use the given jobid from the ns rather than the
RMS jobid
* grab the cellid from the environment, if its there. In reality, this is
probably just another way of setting the cellid to 0, but seems like
a good thing to do...
This commit was SVN r2530.
- see src/util/show_help.h for details (doxygen); main function call
is ompi_show_help()
- text message files are expected to be located in $pkgdatadir
(usually $prefix/share/openmpi). Anyone can install a text file in
$pkgdatadir with their message(s) in it and then have them displayed
via ompi_show_help(). "pkgdata_DATA" is the keyword to use in
Makefile.am's, for example (from src/mca/base/Makefile.am):
pkgdata_DATA = help-mca-base.txt
- added a few examples in the code base using ompi_show_help(), but
not too many -- can convert more "show_help" comments in the code
over time; no huge rush. :-)
- no i18n-like support yet; waiting for advice and consensus from
other developers
This commit was SVN r2519.
it's not going to the testing@open-mpi.org list (correspondingly
remove the subject prefix from the testing@open-mpi.org list config)
- re-add a missing unlink() that was causing problems.
This commit was SVN r2517.
- added src/mpi/f77/strings.[ch] for f<-->c string conversions
- added src/mpi/f77/constants* for instiantiating and providing macros
to check for the various fortran address "constants" (read the
comments in this file -- it's quite complicated, unfortunately :-\ ):
- MPI_BOTTOM
- MPI_ARGV_NULL
- MPI_ARGVS_NULL
- MPI_ERRCODES_IGNORE
- MPI_STATUS_IGNORE
- MPI_STATUSES_IGNORE
- updated fortran MPI_COMM_SET_NAME and MPI_COMM_GET_NAME to check
string handling
- updated fortran MPI_RECV to check MPI_STATUS_IGNORE handling
- updated fortran MPI_COMM_SPAWN to check string and MPI_ARGV_NULL and
MPI_ERRCODES_IGNORE handling
- partially modified src/mpi/f77/prototypes_mpi.h to account for
string length parameters passed by the fortran compiler; more work to
be done there
- backed out a silly previous change in send_f.c by me (duh)
- updated fortran MPI_COMM_DUP and MPI_COMM_FREE to check int<-->fint
macros
This commit was SVN r2512.
