Several updates, including:
* Remove -single dash options
* Don't chmod the whole tree; just chmod the files we're trying to remove
* No more support for SVN or HG; 100% git
* Strengthen the dirty repo checks
* Use git describe for the repo version
* Set tarball_version to "" (i.e., empty) in VERSION
Removed a redundant copy of the scripts running on the build server
and moved the remaining copy out to a top-level directory in contrib
(i.e., contrib/build-server vs. contrib/dist/build-server, where I
never could remember where to find them).
This is a first cut at updating various infrastructure for git. There
will definitely be more commits; some of the scripts require
committed/pushed code (e.g., the various make-tarball scripts). So
it's not possible to know if we got it right without committing/pushing.
We don't use this script any more (we use gitdub now), but it took a
long time to figure this out. So I'm putting this script in git just
so that it's in history if we ever need it again.
Description:
setting mpi_abort_print_stack in mca params file now makes openmpi
unhappy. Comment these out in all the LANL platform files.
Requested by TOSS OpenMPI support person.
cmr=v1.8.3
This commit was SVN r32782.
Have the make_dist_tarball script check to ensure that the source tree
is clean before continuing. This ensures that we don't accidentally
build a distribution tarball with something that is not committed in
the repo.
There is a --dirtyok option to override this check, and if you access
this script via the "make_tarball" link, --dirtyok is added to the
default set of options.
cmr=v1.8.3:reviewer=rhc
This commit was SVN r32623.
The script used to get confused if you ran it in a subdir of the OMPI
tree (e.g., it would report help files not found if source code
referred to a help file that was not under the subdir in which it was
run).
Now the script searches the whole tree for help files, but only
analyzes the source from the subdir in which it was started. Meaning:
it should always find all help files, and won't get confused like it
did before.
This commit was SVN r32548.
Don't use "ompi" names with top-level constructs, because the OMPI
project may not be built. Instead, just use "opal" names -- they'll
always be there.
This commit was SVN r32446.
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
new automake requires subdirs-object directive, to resolve this:
09:43:37 automake: warning: possible forward-incompatibility.
09:43:37 automake: At least a source file is in a subdirectory, but the 'subdir-objects'
09:43:37 automake: automake option hasn't been enabled. For now, the corresponding output
09:43:37 automake: object file(s) will be placed in the top-level directory. However,
09:43:37 automake: this behaviour will change in future Automake versions: they will
09:43:37 automake: unconditionally cause object files to be placed in the same subdirectory
09:43:37 automake: of the corresponding sources.
09:43:37 automake: You are advised to start using 'subdir-objects' option throughout your
09:43:37 automake: project, to avoid future incompatibilities.
09:43:37 tools/otfmerge/Makefile.common:13: warning: source file '$(OTFMERGESRCDIR)/otfmerge.c' is in a subdirectory,
09:43:37 tools/otfmerge/Makefile.common:13: but option 'subdir-objects' is disabled
cmr=v1.8.2:reviewer=ompi-rm1.8
This commit was SVN r32225.
consistency across different distros: src.rpm create on one distro can be unpacked on
another when same packing algorithm used on both.
reviewed by Jeff
cmr=v1.8.2:reviewer=ompi-rm1.8
This commit was SVN r32205.
Update the Open MPI description and fix lots of grammatical errors in
the OpenSHMEM description.
cmr=v1.8.2:reviewer=ompi-rm1.8
This commit was SVN r31709.
* Ensure to cd to the basename of the URL (e.g., "v1.8" from
"branches/v1.8")
* Remove the erroneous -m from the svn commit line that was
preventing the updated .gitignore file from getting committed
This commit was SVN r31548.
Add some getopt options for both build-gitignore.pl and
build-hgignore.pl:
-v: be a little verbose
-h: show a quick help message
-o: specify the output file to write
build-hgignore.pl defaults to writing .hgignore, and
build-gitignore.pl defaults to writing .gitignore. But you can use -o
to specify writing a different filename.
This commit was SVN r31397.
Sort the output from reading directory contents so that the generated
.gitignore and .hgignore files will be much more consistent (and
friendly to change from subsequent runs, especially when they are
committed to SVN/git/hg repos).
This commit was SVN r31394.
