installation directories) in configure, the files that depend on this
information are not properly rebuilt. If you need this information,
don't setup a -D in the Makefile.am - instead, include
opal/install_dirs.h.
* Use the : option in AC_CONFIG_FILES to avoid needing to expose that
we are playing around with temporary files with our headers to avoid
rebuilding
* Clean up the version file information a bit, and like the install
directory stuff, make sure that there is a dependency so that
ompi_info gets rebuilt properly when a version number changes.
This commit was SVN r9256.
was causing problems (indeed, we don't have it in LAM and it hasn't caused
problems in the last many many years). Standard I/O forwarding now works
properly on Solaris in both 32 and 64 bit builds
* Add NEWS item about standard I/O on platforms without openpty()
This commit was SVN r9255.
with MPI_WIN_NULL and the Fortran bindings.
It appears I had already done this, since all the infrastructure was already
in place. I probably edited mpi.h instead of mpi.h.in. Sigh.
This commit was SVN r9228.
This should go to the v1.0 branch with r9223.
This commit was SVN r9224.
The following SVN revision numbers were found above:
r9223 --> open-mpi/ompi@d71750d073
still allows its state to be modified (Solaris on Opteron, for example),
so we need to copy the va_list if we are going to use it twice. Fixes
a segfault on Opteron Solaris. Thanks to Pierre Valiron for reporting
the issue and for providing access for testing.
This needs to go to the 1.0 branch.
This commit was SVN r9223.
of the string. Since it is relevant fix, however not affecting any other
part of the source code, should probably still go onto the 1.0 branch.
This commit was SVN r9214.
now-default GNU debug flags (-g3) don't accidentally cause the
configure system to add -O3 to the build flags (because it didn't
recognize that -g3 was a debugging flag).
This commit was SVN r9207.
Still release the standard stream upon finalizing.
This commit was SVN r9204.
The following SVN revision numbers were found above:
r9182 --> open-mpi/ompi@a2a26525b3
case still compile properly, even though these bindings were wrong. :-(
- Both interface functions are necessary.
- I accidentally had a subroutine interface named the same thing as the
back-end F77 function -- a definite no-no. Ensure that all F90
interface functions have a suffix to make them different than the
back-end F77 function names.
- Also parameterize the output() subroutine on the type of the argvs
parameter to switch between the character arrays and the integer.
This commit was SVN r9202.
for the C++ bindings in MPI-2 p276-278 to see that MPI_BOOL should
work with MPI_LAND, MPI_LOR, and MPI_LXOR. Thanks to Andy Selle for
pointing this out.
This commit was SVN r9200.
they will match the prototypes in the [styictly-typed] MPI F90
bindings. Specifically, fix up MPI_COMM_SPAWN and
MPI_COMM_SPAWN_MULTIPLE so that the constants MPI_ARGV_NULL,
MPI_ERRCODES_IGNORE, and MPI_ARGVS_NULL can be used in the F90
bindings. Thanks to Michael Kluskens for pointing this out to us.
Some work still remains in the F90 bindings -- we are missing all
places where choice buffers can be of type CHARACTER.
This commit was SVN r9198.
add an explicit test case that checks for them. It is necessary to
put this test function here because the OMPI_IS* macros are only
defined in this directory.
This commit was SVN r9195.
and assert it is below when accessing ompi_ddt_basicDatatypes
- datatype in ompi_ddt_pack_description_length is and will not be
changed.
This commit was SVN r9193.
