than expected versions of tools are found. make_dist_tarball will
''not'' accept lower or higher versions by default (since the goal is
exact reproducability, after all), but you can specify the --highok
command line switch to allow it.
I'm also removing make_tarball in this commit and will replace it with
a sym link to make_dist_tarball in the next commit. The script will
default to allowing higher versions of the tools when invoked with an
argv[0] of "make tarball" (i.e., --highok is not necessary, but is
harmless).
This commit was SVN r21530.
OMPI_* to OPAL_*. This allows opal layer to be used more independent
from the whole of ompi.
NOTE: 9 "svn mv" operations immediately follow this commit.
This commit was SVN r21180.
the v1.3 branch's r19812:
Update the make_dist_tarball script to check for the proper GNU tool
versions as posted on http://www.open-mpi.org/svn/building.php
* m4 1.4.11
* autoconf 2.63
* automake 1.10.1
* libtool 2.2.6
This commit was SVN r19813.
The following SVN revision numbers were found above:
r19812 --> open-mpi/ompi@706923f7b1
OMPI trunk. Need all organizations to ensure I got spellings and
affiliations correct.
Also commit a helper script to help keep AUTHORS up to date on the
trunk; it should be run before we create release branches.
This commit was SVN r19612.
* Make the creation of the build dir for the man pages a bit more
robust (thanks to suggestions from Ralf W.).
* Only distribute the .Xin files, not the .X man pages themselves.
* Make the .X files depend on opal_config.h so that if you re-run
configure and change opal_config.h (e.g., a new version), the man
pages should get rebuilt.
* Man pages are now cleaned with "distclean", not "maintainer-clean".
* Fix a typo in opal_crs.7in.
* Udpate make_dist_tarball to update "date" in the VERSION file.
* Make make_dist_tarball a bit friendlier to hg checkouts.
This commit was SVN r19219.
Update the make_dist_tarball script and the HACKING file to the new trunk
autotools requirements, including the addition of a specific m4 version:
* m4 1.4.11
* autoconf 2.62
* automake 1.10.1
* libtool 2.2.4
This commit was SVN r18465.
The following Trac tickets were found above:
Ticket 1265 --> https://svn.open-mpi.org/trac/ompi/ticket/1265
* Remove duplicate %{_sysconfdir} in the % files sections when
building the sub-packages.
* When building the sub-packages, ensure that devel.files also picks
up the F90 module.
* Hard-code the directory name "openmpi" into _pkglibdir (vs. using
%{name}) because the OMPI code base has it hard-coded as well.
Thanks to Jim Kusznir for noticing the problem.
This commit was SVN r17036.
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.
- 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.
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.
