1
1
openmpi/contrib/dist/linux
2010-02-22 07:47:30 +00:00
..
buildrpm.sh add ext variables to control script behave 2009-01-13 08:50:18 +00:00
buildswitcherrpm.sh Also allow .tar.bz2 files to snarf the version 2006-06-29 19:52:38 +00:00
ompi-spec-generator.py - fix broken build target, we have to use the files in the RPM build 2007-10-24 17:48:30 +00:00
openmpi-switcher-modulefile.spec - Added a missing original entry in the changelog 2006-07-02 12:08:48 +00:00
openmpi-switcher-modulefile.tcl Name change 2006-04-27 03:33:08 +00:00
openmpi.spec remove trailing colon at the end of the generated LD_LIBRARY_PATH 2010-02-22 07:47:30 +00:00
README - Add missing executables to specfile (ompi-server, etc.) 2009-12-14 19:52:23 +00:00
README.ompi-spec-generator Just do a little word wrapping. 2007-07-12 19:02:01 +00:00

Copyright (c) 2004-2006 The Trustees of Indiana University and Indiana
                        University Research and Technology
                        Corporation.  All rights reserved.
Copyright (c) 2004-2006 The University of Tennessee and The University
                        of Tennessee Research Foundation.  All rights
                        reserved.
Copyright (c) 2004-2006 High Performance Computing Center Stuttgart, 
                        University of Stuttgart.  All rights reserved.
Copyright (c) 2004-2006 The Regents of the University of California.
                        All rights reserved.
Copyright (c) 2006-2009 Cisco Systems, Inc.  All rights reserved.
$COPYRIGHT$

Additional copyrights may follow

$HEADER$

===========================================================================

The buildrpm.sh script takes a single argument -- a filename pointing
to an Open MPI tarball (may be either .gz or .bz2).  It will create
one or more RPMs from this tarball:

1. Source RPM
2. "All in one" RPM, where all of Open MPI is put into a single RPM.
3. "Multiple" RPM, where Open MPI is split into several sub-package
   RPMs:
   - openmpi-runtime
   - openmpi-devel
   - openmpi-docs

The prefix, target architecture, and choice of RPM(s) to build are all
currently hard-coded in the beginning of the buildrpm.sh script.

Alternatively, you can build directly from the openmpi.spec spec file
or SRPM directly.  Many options can be passed to the building process
via rpmbuild's --define option (there are older versions of rpmbuild
that do not seem to handle --define'd values properly in all cases,
but we generally don't care about those old versions of rpmbuild...).
The available options are described in the comments in the beginning
of the spec file in this directory.