Add support for Cray cross compile systems (otherwise configure fails)
This commit was SVN r15136.
The following SVN revision numbers were found above:
r15133 --> open-mpi/ompi@d3372729bb
use_default_rpm_opt_flags. It defaults to a value of 1, meaning that
we'll try to use $RPM_OPT_FLAGS. But if you're not compiling with the
GNU compilers, you might want to set this value to 0 so that your
compiler doesn't get flags that it doesn't understand (e.g., PGI 7.0
will barf on flags that it doesn't understand).
This commit was SVN r14477.
finally brings in functionality that is already on the 1.2 branch, and
was developed and tested in the v1.2ofed branch (and other places).
Short version of new features:
* Support for ibv_fork_init()
* Automatically fill in the openib BTL bandwidth value by
querying the HCA port
* Installdirs functionality
* Fixes to always use -I in the Fortran wrapper compilers (#924)
* Gleb's mpool updates
* Remove some kruft in btl/openib/configure.m4, therefore
fixing the harmless warnings noted in #665
* Bunches of updates to the Linux RPM spec file
I.e., effectively the same thing that r14411 brought to the v1.2
branch.
Also effectively brought in r14432 and r14433 (some fixes on top of
the original r14411 commit to v1.2). Still need to bring in the moral
equivalent of r14445 after this commit (fixes to installdirs).
This commit was SVN r14449.
The following SVN revision numbers were found above:
r14411 --> open-mpi/ompi@83b31314ae
r14432 --> open-mpi/ompi@a48f160595
r14433 --> open-mpi/ompi@68f346d2bc
r14445 --> open-mpi/ompi@13d366b827
include the fixes to the backtrace and signal handler code for x86_64 builds,
so no need to disable them in the configure code.
This commit was SVN r14278.
while LAM/MPI was at IU (well after it was at Notre Dame or OSC). I wrote
the original version, so I am positive of this fact. The ND and OSC
copyrights should never have been committed into the LAM/MPI tree, much
less the Open MPI tree as this code has no origin with either institution.
The bulk of the script was developed at Indiana University (again, almost
entirely by myself), with later additions after I moved to Los Alamos.
This commit was SVN r14277.
- Remove OMPI_VER_PACKAGE from the user-editable configuration
stuff -- users shouldn't ever need to deal with it
- Disable the stack trace stuff, since it causes problems
on 64 bit Intel builds
- Only include binaries for 32 bit platforms, but libraries
for 32 and 64 bit platforms
- Print more information about build configuration during
the start of the script
This commit was SVN r14276.
This merge adds Checkpoint/Restart support to Open MPI. The initial
frameworks and components support a LAM/MPI-like implementation.
This commit follows the risk assessment presented to the Open MPI core
development group on Feb. 22, 2007.
This commit closes trac:158
More details to follow.
This commit was SVN r14051.
The following SVN revisions from the original message are invalid or
inconsistent and therefore were not cross-referenced:
r13912
The following Trac tickets were found above:
Ticket 158 --> https://svn.open-mpi.org/trac/ompi/ticket/158
- mca_base_param_file_prefix
(Default: NULL)
This is the fullname of the "-am" mpirun option. Used to specify a ':'
separated list of AMCA parameter set files.
- mca_base_param_file_path
(Default: $SYSCONFDIR/amca-param-sets/:$CWD)
The path to search for AMCA files with relative paths. A warning will be
printed if the AMCA file cannot be found.
* Added a new function "mca_base_param_recache_files" the re-reads the file
configurations. This is used internally to help bootstrap the MCA system.
* Added a new orterun/mpirun command line option '-am' that aliases for the
mca_base_param_file_prefix MCA parameter
* Exposed the opal_path_access function as it is generally useful in other
places in the code.
* New function "opal_cmd_line_make_opt_mca" which will allow you to append a
new command line option with MCA parameter identifiers to set at the same
time. Previously this could only be done at command line declaration time.
* Added a new directory under the $pkgdatadir named "amca-param-sets" where all
the 'shipped with' Open MPI AMCA parameter sets are placed. This is the first
place to search for AMCA sets with relative paths.
* An example.conf AMCA parameter set file is located in
contrib/amca-param-sets/.
* Jeff Squyres contributed an OpenIB AMCA set for benchmarking.
Note: You will need to autogen with this commit as it adds a configure param.
Sorry :(
This commit was SVN r13867.
- only include binaries for ppc/i386 -- no need for 64 bit
- default to not printing load errors so that the XGrid pls
doesn't cause errors when doing 64 bit builds
This commit was SVN r13577.
* Separate out test clauses; don't have the same guarantees of
left-to-right evaluation in shell script that you do in other
languages (i.e., protect against the case of running "basename ''")
This commit was SVN r13463.
- The Verification check only checked that a file that's in SVN is there,
which AM would have complained about during make dist, so it's really
a pointless check
- No need to remove / restore autogen.sh, as AM isn't going to put it
in the tarball anyway, and even if it would, this thing would only
cause it to fail during make dist. All this step did was erase any
changes you had to autogen.sh when you run make_dist_tarball, which
really sucks.
This commit was SVN r13307.
deploy: will create a full binary distribution (.msi file)
ompi-small: will create an update binary distribution(
no include files, nothing else except the libs and execs).
ompi_install.sh: sh script to install manually into a specific
target directory.
This commit was SVN r12589.
little bit from the prior commit (r12051).
This commit was SVN r12052.
The following SVN revision numbers were found above:
r12051 --> open-mpi/ompi@72e202a432
* OFED bug 249 (http://openib.org/bugzilla/show_bug.cgi?id=249) where
Suse systems automatically add "-D_FORTIFY_SOURCE=2" to the
RPM_OPT_FLAGS, which works fine when you're compiling with gcc.
But not so much when using other compilers (_FORTIFY source
silently changes the names of functions like memcpy() in an attempt
to protect against buffer overflows, and uses a gcc __builtin
thingy that results in undefined symbols when you compile/link with
other compilers, such as icc -- as of 6 Oct 2006). So do some
horrid huersitics to see if we're using gcc, and if so, sed out any
FORTIFY_SOURCE stuff in RPM_OPT_FLAGS.
* If we're building a single rpm, don't bother creating the
runtime.files and devel.files files. And if we are making multiple
RPMs, then ensure to end the pipe chain with /bin/true so that if
the user specified --enable-static --disable-shared and the egrep
for *.so files fails, the return status from egrep (1) doesn't
cause RPM to barf. Specifically, do this so that /bin/true's
return value of 0 is always what rpmbuild sees, regardless of the
return status of egrep:
{{{
find $RPM_BUILD_ROOT -type f -o -type l | \
sed -e "s@$RPM_BUILD_ROOT@@" | \
egrep "lib.*\.a|lib.*\.la" > devel.files | /bin/true
}}}
This commit was SVN r12051.
* Remove LANL section; they don't want it
* Add some help for OFED building
* Remove some outdated "rm -f" lines for executables that we no longer
ship
This commit was SVN r12046.
* Print a warning error message if a target is not in an exposure epoch
and an update is received. This results in the app continuing with
that call having never happened, rather than evil hangs.
refs trac:325
This commit was SVN r11514.
The following Trac tickets were found above:
Ticket 325 --> https://svn.open-mpi.org/trac/ompi/ticket/325
backwards -- should have done the work on the trunk and merged to the
v1.1 branch).
This commit was SVN r11447.
The following SVN revision numbers were found above:
r11434 --> open-mpi/ompi@50d1587b10
r11444 --> open-mpi/ompi@bb4d7fac0e
