--- mpich2-1.2.1.1.orig/debian/libmpe-mpich2-dev.docs +++ mpich2-1.2.1.1/debian/libmpe-mpich2-dev.docs @@ -0,0 +1,2 @@ +debian/tmp/usr/share/doc/jumpshot-4/usersguide.pdf +debian/tmp/usr/share/doc/jumpshot-4/html --- mpich2-1.2.1.1.orig/debian/libmpich2-dev.install +++ mpich2-1.2.1.1/debian/libmpich2-dev.install @@ -0,0 +1,14 @@ +etc/mpich2/mpi*.conf +usr/bin/mpic++ +usr/bin/mpicc +usr/bin/mpich2version +usr/bin/mpicxx +usr/bin/mpif77 +usr/bin/mpif90 +usr/lib/lib*mpich*.a +usr/lib/lib*mpich*.so +usr/lib/lib*opa* +usr/lib/pkgconfig/mpich2-ch3.pc +usr/include/mpich2/opa* +usr/include/mpich2/mpi* +usr/include/mpich2/primitives/ --- mpich2-1.2.1.1.orig/debian/libmpich2-dev.links +++ mpich2-1.2.1.1/debian/libmpich2-dev.links @@ -0,0 +1,3 @@ +usr/lib/libmpich.so.1.2 usr/lib/libmpich.so +usr/lib/libfmpich.so.1.2 usr/lib/libfmpich.so +usr/share/man/man1/mpicxx.1.gz /usr/share/man/man1/mpic++.1.gz --- mpich2-1.2.1.1.orig/debian/mpich2.manpages +++ mpich2-1.2.1.1/debian/mpich2.manpages @@ -0,0 +1,3 @@ +debian/tmp/usr/share/man/man1/MPI.1 +debian/tmp/usr/share/man/man1/mpiexec.1 +debian/tmp/usr/share/man/man1/mpd* --- mpich2-1.2.1.1.orig/debian/README.Debian +++ mpich2-1.2.1.1/debian/README.Debian @@ -0,0 +1,14 @@ +MPICH2 for Debian +================= + +MPI Alternatives +---------------- +This package uses the Debian Alternatives system to allow you to choose +between the different MPI implementations. + +You can check which version of MPI you use with + update-alternatives --list mpirun + update-alternatives --list mpi (for the development files) + +Use 'update-alternatives --display' to list all installed implementations, +and 'update-alternatives --config' to configure which implementation to use. --- mpich2-1.2.1.1.orig/debian/libmpe-mpich2-dev.install +++ mpich2-1.2.1.1/debian/libmpe-mpich2-dev.install @@ -0,0 +1,17 @@ +etc/mpich2/mpe* +usr/include/mpich2/mpe* +usr/include/mpich2/clog* +usr/share/man/man4 +usr/lib/*mpe* +usr/lib/clog* +usr/lib/slog* +usr/lib/log* +usr/lib/jumpshot* +usr/lib/trace* +usr/sbin/mpe* +usr/bin/slog* +usr/bin/mpe* +usr/bin/jumpshot +usr/bin/log* +usr/bin/clog* +usr/bin/check_callstack --- mpich2-1.2.1.1.orig/debian/mpich2.postinst +++ mpich2-1.2.1.1/debian/mpich2.postinst @@ -0,0 +1,40 @@ +#!/bin/sh + +set -e + +case "$1" in + configure) + # Continue below + ;; + abort-upgrade|abort-remove|abort-deconfigure) + exit 0; + ;; + *) + echo "postinst called with unknown argument \`$1'" >&2 + exit 0; + ;; +esac + +# so, we are running with $1 = configure +# mpich2 versions before 1.2.1~rc1-1 were using two alternatives where other +# MPI implementations were using only one, which breaks. Clean up +# our mess. +if [ "$2" != "" ] && dpkg --compare-versions "$2" le "1.2.1~rc1-1"; then + update-alternatives --remove mpiexec /usr/bin/mpiexec.mpich2 +fi +if update-alternatives --list mpiexec > /dev/null 2>&1; then + # OK, that case sucks. Apparently, we still have a mpiexec alternative, maybe + # from a different package (like openmpi). In that case, the only thing we + # can do is --remove-all... + update-alternatives --remove-all mpiexec +fi + +update-alternatives \ + --install /usr/bin/mpirun mpirun /usr/bin/mpirun.mpich2 40 \ + --slave /usr/share/man/man1/mpirun.1.gz mpirun.1.gz /usr/share/man/man1/mpirun.mpich2.1.gz \ + --slave /usr/bin/mpiexec mpiexec /usr/bin/mpiexec.mpich2 \ + --slave /usr/share/man/man1/mpiexec.1.gz mpiexec.1.gz /usr/share/man/man1/mpiexec.mpich2.1.gz + +#DEBHELPER# + +exit 0 --- mpich2-1.2.1.1.orig/debian/mpich2-doc.examples +++ mpich2-1.2.1.1/debian/mpich2-doc.examples @@ -0,0 +1,4 @@ +debian/tmp/usr/share/examples_collchk +debian/tmp/usr/share/examples_graphics +debian/tmp/usr/share/examples_logging +debian/tmp/usr/share/logfiles --- mpich2-1.2.1.1.orig/debian/libmpich2-dev.postinst +++ mpich2-1.2.1.1/debian/libmpich2-dev.postinst @@ -0,0 +1,37 @@ +#!/bin/sh + +set -e + +case "$1" in + configure) + # Continue below + ;; + abort-upgrade|abort-remove|abort-deconfigure) + exit 0; + ;; + *) + echo "postinst called with unknown argument \`$1'" >&2 + exit 0; + ;; +esac + +update-alternatives \ + --install /usr/include/mpi mpi /usr/include/mpich2 40 \ + --slave /usr/lib/libmpi.so libmpi.so /usr/lib/libmpich.so \ + --slave /usr/lib/libmpi++.so libmpi++.so /usr/lib/libmpichcxx.so \ + --slave /usr/lib/libmpif77.so libmpif77.so /usr/lib/libfmpich.so \ + --slave /usr/lib/libmpif90.so libmpif90.so /usr/lib/libmpichf90.so \ + --slave /usr/bin/mpicc mpicc /usr/bin/mpicc.mpich2 \ + --slave /usr/bin/mpic++ mpic++ /usr/bin/mpic++.mpich2 \ + --slave /usr/bin/mpicxx mpicxx /usr/bin/mpicxx.mpich2 \ + --slave /usr/bin/mpif77 mpif77 /usr/bin/mpif77.mpich2 \ + --slave /usr/bin/mpif90 mpif90 /usr/bin/mpif90.mpich2 \ + --slave /usr/share/man/man1/mpicc.1.gz mpicc.1.gz /usr/share/man/man1/mpicc.mpich2.1.gz \ + --slave /usr/share/man/man1/mpic++.1.gz mpic++.1.gz /usr/share/man/man1/mpic++.mpich2.1.gz \ + --slave /usr/share/man/man1/mpicxx.1.gz mpicxx.1.gz /usr/share/man/man1/mpicxx.mpich2.1.gz \ + --slave /usr/share/man/man1/mpif77.1.gz mpif77.1.gz /usr/share/man/man1/mpif77.mpich2.1.gz \ + --slave /usr/share/man/man1/mpif90.1.gz mpif90.1.gz /usr/share/man/man1/mpif90.mpich2.1.gz + +#DEBHELPER# + +exit 0 --- mpich2-1.2.1.1.orig/debian/libmpich2-dev.manpages +++ mpich2-1.2.1.1/debian/libmpich2-dev.manpages @@ -0,0 +1,4 @@ +debian/tmp/usr/share/man/man1/mpicc.1 +debian/tmp/usr/share/man/man1/mpicxx.1 +debian/tmp/usr/share/man/man1/mpif77.1 +debian/tmp/usr/share/man/man1/mpif90.1 --- mpich2-1.2.1.1.orig/debian/copyright +++ mpich2-1.2.1.1/debian/copyright @@ -0,0 +1,600 @@ +This package was debianized by Lucas Nussbaum on +Mon Oct 12 21:20:39 CEST 2009. + +This work was heavily based on packaging work by Zach Lowry +and Muammar El Khatib . + +It was downloaded from the ANL MPICH2 website at: + http://www.mcs.anl.gov/research/projects/mpich2/downloads/index.php?s=downloads + +Upstream Authors: The MPICH2 Team at Argonne National Laboratory + +Copyright Notice + + 2002 University of Chicago + +<----- Start of COPYRIGHT file -----> + COPYRIGHT + +The following is a notice of limited availability of the code, and disclaimer +which must be included in the prologue of the code and in all source listings +of the code. + +Copyright Notice + + 2002 University of Chicago + +Permission is hereby granted to use, reproduce, prepare derivative works, and +to redistribute to others. This software was authored by: + +Argonne National Laboratory Group +W. Gropp: (630) 252-4318; FAX: (630) 252-5986; e-mail: gropp@mcs.anl.gov +E. Lusk: (630) 252-7852; FAX: (630) 252-5986; e-mail: lusk@mcs.anl.gov +Mathematics and Computer Science Division +Argonne National Laboratory, Argonne IL 60439 + + + GOVERNMENT LICENSE + +Portions of this material resulted from work developed under a U.S. +Government Contract and are subject to the following license: the Government +is granted for itself and others acting on its behalf a paid-up, nonexclusive, +irrevocable worldwide license in this computer software to reproduce, prepare +derivative works, and perform publicly and display publicly. + + DISCLAIMER + +This computer code material was prepared, in part, as an account of work +sponsored by an agency of the United States Government. Neither the United +States, nor the University of Chicago, nor any of their employees, makes any +warranty express or implied, or assumes any legal liability or responsibility +for the accuracy, completeness, or usefulness of any information, apparatus, +product, or process disclosed, or represents that its use would not infringe +privately owned rights. + +Portions of this code were written by Microsoft. Those portions are +Copyright (c) 2007 Microsoft Corporation. Microsoft grants permission to +use, reproduce, prepare derivative works, and to redistribute to +others. The code is licensed "as is." The User bears the risk of using +it. Microsoft gives no express warranties, guarantees or +conditions. To the extent permitted by law, Microsoft excludes the +implied warranties of merchantability, fitness for a particular +purpose and non-infringement. + +<----- End of COPYRIGHT file -----> + +There are also some files in contrib/knem that are licensed differently. +Copyright notice: + * Copyright © INRIA 2009 + * Brice Goglin + * + * This software is a computer program whose purpose is to provide + * a fast inter-process communication subsystem. + * + * This software is governed by the CeCILL-B license under French law and + * abiding by the rules of distribution of free software. You can use, + * modify and/ or redistribute the software under the terms of the CeCILL-B + * license as circulated by CEA, CNRS and INRIA at the following URL + * "http://www.cecill.info". + +This code is released under the CeCILL-B license, which is similar to the +BSD license. + +<----- Start of the COPYING file in contrib/knem/ ------> +CeCILL-B FREE SOFTWARE LICENSE AGREEMENT + + + Notice + +This Agreement is a Free Software license agreement that is the result +of discussions between its authors in order to ensure compliance with +the two main principles guiding its drafting: + + * firstly, compliance with the principles governing the distribution + of Free Software: access to source code, broad rights granted to + users, + * secondly, the election of a governing law, French law, with which + it is conformant, both as regards the law of torts and + intellectual property law, and the protection that it offers to + both authors and holders of the economic rights over software. + +The authors of the CeCILL-B (for Ce[a] C[nrs] I[nria] L[ogiciel] L[ibre]) +license are: + +Commissariat à l'Energie Atomique - CEA, a public scientific, technical +and industrial research establishment, having its principal place of +business at 25 rue Leblanc, immeuble Le Ponant D, 75015 Paris, France. + +Centre National de la Recherche Scientifique - CNRS, a public scientific +and technological establishment, having its principal place of business +at 3 rue Michel-Ange, 75794 Paris cedex 16, France. + +Institut National de Recherche en Informatique et en Automatique - +INRIA, a public scientific and technological establishment, having its +principal place of business at Domaine de Voluceau, Rocquencourt, BP +105, 78153 Le Chesnay cedex, France. + + + Preamble + +This Agreement is an open source software license intended to give users +significant freedom to modify and redistribute the software licensed +hereunder. + +The exercising of this freedom is conditional upon a strong obligation +of giving credits for everybody that distributes a software +incorporating a software ruled by the current license so as all +contributions to be properly identified and acknowledged. + +In consideration of access to the source code and the rights to copy, +modify and redistribute granted by the license, users are provided only +with a limited warranty and the software's author, the holder of the +economic rights, and the successive licensors only have limited liability. + +In this respect, the risks associated with loading, using, modifying +and/or developing or reproducing the software by the user are brought to +the user's attention, given its Free Software status, which may make it +complicated to use, with the result that its use is reserved for +developers and experienced professionals having in-depth computer +knowledge. Users are therefore encouraged to load and test the +suitability of the software as regards their requirements in conditions +enabling the security of their systems and/or data to be ensured and, +more generally, to use and operate it in the same conditions of +security. This Agreement may be freely reproduced and published, +provided it is not altered, and that no provisions are either added or +removed herefrom. + +This Agreement may apply to any or all software for which the holder of +the economic rights decides to submit the use thereof to its provisions. + + + Article 1 - DEFINITIONS + +For the purpose of this Agreement, when the following expressions +commence with a capital letter, they shall have the following meaning: + +Agreement: means this license agreement, and its possible subsequent +versions and annexes. + +Software: means the software in its Object Code and/or Source Code form +and, where applicable, its documentation, "as is" when the Licensee +accepts the Agreement. + +Initial Software: means the Software in its Source Code and possibly its +Object Code form and, where applicable, its documentation, "as is" when +it is first distributed under the terms and conditions of the Agreement. + +Modified Software: means the Software modified by at least one +Contribution. + +Source Code: means all the Software's instructions and program lines to +which access is required so as to modify the Software. + +Object Code: means the binary files originating from the compilation of +the Source Code. + +Holder: means the holder(s) of the economic rights over the Initial +Software. + +Licensee: means the Software user(s) having accepted the Agreement. + +Contributor: means a Licensee having made at least one Contribution. + +Licensor: means the Holder, or any other individual or legal entity, who +distributes the Software under the Agreement. + +Contribution: means any or all modifications, corrections, translations, +adaptations and/or new functions integrated into the Software by any or +all Contributors, as well as any or all Internal Modules. + +Module: means a set of sources files including their documentation that +enables supplementary functions or services in addition to those offered +by the Software. + +External Module: means any or all Modules, not derived from the +Software, so that this Module and the Software run in separate address +spaces, with one calling the other when they are run. + +Internal Module: means any or all Module, connected to the Software so +that they both execute in the same address space. + +Parties: mean both the Licensee and the Licensor. + +These expressions may be used both in singular and plural form. + + + Article 2 - PURPOSE + +The purpose of the Agreement is the grant by the Licensor to the +Licensee of a non-exclusive, transferable and worldwide license for the +Software as set forth in Article 5 hereinafter for the whole term of the +protection granted by the rights over said Software. + + + Article 3 - ACCEPTANCE + +3.1 The Licensee shall be deemed as having accepted the terms and +conditions of this Agreement upon the occurrence of the first of the +following events: + + * (i) loading the Software by any or all means, notably, by + downloading from a remote server, or by loading from a physical + medium; + * (ii) the first time the Licensee exercises any of the rights + granted hereunder. + +3.2 One copy of the Agreement, containing a notice relating to the +characteristics of the Software, to the limited warranty, and to the +fact that its use is restricted to experienced users has been provided +to the Licensee prior to its acceptance as set forth in Article 3.1 +hereinabove, and the Licensee hereby acknowledges that it has read and +understood it. + + + Article 4 - EFFECTIVE DATE AND TERM + + + 4.1 EFFECTIVE DATE + +The Agreement shall become effective on the date when it is accepted by +the Licensee as set forth in Article 3.1. + + + 4.2 TERM + +The Agreement shall remain in force for the entire legal term of +protection of the economic rights over the Software. + + + Article 5 - SCOPE OF RIGHTS GRANTED + +The Licensor hereby grants to the Licensee, who accepts, the following +rights over the Software for any or all use, and for the term of the +Agreement, on the basis of the terms and conditions set forth hereinafter. + +Besides, if the Licensor owns or comes to own one or more patents +protecting all or part of the functions of the Software or of its +components, the Licensor undertakes not to enforce the rights granted by +these patents against successive Licensees using, exploiting or +modifying the Software. If these patents are transferred, the Licensor +undertakes to have the transferees subscribe to the obligations set +forth in this paragraph. + + + 5.1 RIGHT OF USE + +The Licensee is authorized to use the Software, without any limitation +as to its fields of application, with it being hereinafter specified +that this comprises: + + 1. permanent or temporary reproduction of all or part of the Software + by any or all means and in any or all form. + + 2. loading, displaying, running, or storing the Software on any or + all medium. + + 3. entitlement to observe, study or test its operation so as to + determine the ideas and principles behind any or all constituent + elements of said Software. This shall apply when the Licensee + carries out any or all loading, displaying, running, transmission + or storage operation as regards the Software, that it is entitled + to carry out hereunder. + + + 5.2 ENTITLEMENT TO MAKE CONTRIBUTIONS + +The right to make Contributions includes the right to translate, adapt, +arrange, or make any or all modifications to the Software, and the right +to reproduce the resulting software. + +The Licensee is authorized to make any or all Contributions to the +Software provided that it includes an explicit notice that it is the +author of said Contribution and indicates the date of the creation thereof. + + + 5.3 RIGHT OF DISTRIBUTION + +In particular, the right of distribution includes the right to publish, +transmit and communicate the Software to the general public on any or +all medium, and by any or all means, and the right to market, either in +consideration of a fee, or free of charge, one or more copies of the +Software by any means. + +The Licensee is further authorized to distribute copies of the modified +or unmodified Software to third parties according to the terms and +conditions set forth hereinafter. + + + 5.3.1 DISTRIBUTION OF SOFTWARE WITHOUT MODIFICATION + +The Licensee is authorized to distribute true copies of the Software in +Source Code or Object Code form, provided that said distribution +complies with all the provisions of the Agreement and is accompanied by: + + 1. a copy of the Agreement, + + 2. a notice relating to the limitation of both the Licensor's + warranty and liability as set forth in Articles 8 and 9, + +and that, in the event that only the Object Code of the Software is +redistributed, the Licensee allows effective access to the full Source +Code of the Software at a minimum during the entire period of its +distribution of the Software, it being understood that the additional +cost of acquiring the Source Code shall not exceed the cost of +transferring the data. + + + 5.3.2 DISTRIBUTION OF MODIFIED SOFTWARE + +If the Licensee makes any Contribution to the Software, the resulting +Modified Software may be distributed under a license agreement other +than this Agreement subject to compliance with the provisions of Article +5.3.4. + + + 5.3.3 DISTRIBUTION OF EXTERNAL MODULES + +When the Licensee has developed an External Module, the terms and +conditions of this Agreement do not apply to said External Module, that +may be distributed under a separate license agreement. + + + 5.3.4 CREDITS + +Any Licensee who may distribute a Modified Software hereby expressly +agrees to: + + 1. indicate in the related documentation that it is based on the + Software licensed hereunder, and reproduce the intellectual + property notice for the Software, + + 2. ensure that written indications of the Software intended use, + intellectual property notice and license hereunder are included in + easily accessible format from the Modified Software interface, + + 3. mention, on a freely accessible website describing the Modified + Software, at least throughout the distribution term thereof, that + it is based on the Software licensed hereunder, and reproduce the + Software intellectual property notice, + + 4. where it is distributed to a third party that may distribute a + Modified Software without having to make its source code + available, make its best efforts to ensure that said third party + agrees to comply with the obligations set forth in this Article . + +If the Software, whether or not modified, is distributed with an +External Module designed for use in connection with the Software, the +Licensee shall submit said External Module to the foregoing obligations. + + + 5.3.5 COMPATIBILITY WITH THE CeCILL AND CeCILL-C LICENSES + +Where a Modified Software contains a Contribution subject to the CeCILL +license, the provisions set forth in Article 5.3.4 shall be optional. + +A Modified Software may be distributed under the CeCILL-C license. In +such a case the provisions set forth in Article 5.3.4 shall be optional. + + + Article 6 - INTELLECTUAL PROPERTY + + + 6.1 OVER THE INITIAL SOFTWARE + +The Holder owns the economic rights over the Initial Software. Any or +all use of the Initial Software is subject to compliance with the terms +and conditions under which the Holder has elected to distribute its work +and no one shall be entitled to modify the terms and conditions for the +distribution of said Initial Software. + +The Holder undertakes that the Initial Software will remain ruled at +least by this Agreement, for the duration set forth in Article 4.2. + + + 6.2 OVER THE CONTRIBUTIONS + +The Licensee who develops a Contribution is the owner of the +intellectual property rights over this Contribution as defined by +applicable law. + + + 6.3 OVER THE EXTERNAL MODULES + +The Licensee who develops an External Module is the owner of the +intellectual property rights over this External Module as defined by +applicable law and is free to choose the type of agreement that shall +govern its distribution. + + + 6.4 JOINT PROVISIONS + +The Licensee expressly undertakes: + + 1. not to remove, or modify, in any manner, the intellectual property + notices attached to the Software; + + 2. to reproduce said notices, in an identical manner, in the copies + of the Software modified or not. + +The Licensee undertakes not to directly or indirectly infringe the +intellectual property rights of the Holder and/or Contributors on the +Software and to take, where applicable, vis-à-vis its staff, any and all +measures required to ensure respect of said intellectual property rights +of the Holder and/or Contributors. + + + Article 7 - RELATED SERVICES + +7.1 Under no circumstances shall the Agreement oblige the Licensor to +provide technical assistance or maintenance services for the Software. + +However, the Licensor is entitled to offer this type of services. The +terms and conditions of such technical assistance, and/or such +maintenance, shall be set forth in a separate instrument. Only the +Licensor offering said maintenance and/or technical assistance services +shall incur liability therefor. + +7.2 Similarly, any Licensor is entitled to offer to its licensees, under +its sole responsibility, a warranty, that shall only be binding upon +itself, for the redistribution of the Software and/or the Modified +Software, under terms and conditions that it is free to decide. Said +warranty, and the financial terms and conditions of its application, +shall be subject of a separate instrument executed between the Licensor +and the Licensee. + + + Article 8 - LIABILITY + +8.1 Subject to the provisions of Article 8.2, the Licensee shall be +entitled to claim compensation for any direct loss it may have suffered +from the Software as a result of a fault on the part of the relevant +Licensor, subject to providing evidence thereof. + +8.2 The Licensor's liability is limited to the commitments made under +this Agreement and shall not be incurred as a result of in particular: +(i) loss due the Licensee's total or partial failure to fulfill its +obligations, (ii) direct or consequential loss that is suffered by the +Licensee due to the use or performance of the Software, and (iii) more +generally, any consequential loss. In particular the Parties expressly +agree that any or all pecuniary or business loss (i.e. loss of data, +loss of profits, operating loss, loss of customers or orders, +opportunity cost, any disturbance to business activities) or any or all +legal proceedings instituted against the Licensee by a third party, +shall constitute consequential loss and shall not provide entitlement to +any or all compensation from the Licensor. + + + Article 9 - WARRANTY + +9.1 The Licensee acknowledges that the scientific and technical +state-of-the-art when the Software was distributed did not enable all +possible uses to be tested and verified, nor for the presence of +possible defects to be detected. In this respect, the Licensee's +attention has been drawn to the risks associated with loading, using, +modifying and/or developing and reproducing the Software which are +reserved for experienced users. + +The Licensee shall be responsible for verifying, by any or all means, +the suitability of the product for its requirements, its good working +order, and for ensuring that it shall not cause damage to either persons +or properties. + +9.2 The Licensor hereby represents, in good faith, that it is entitled +to grant all the rights over the Software (including in particular the +rights set forth in Article 5). + +9.3 The Licensee acknowledges that the Software is supplied "as is" by +the Licensor without any other express or tacit warranty, other than +that provided for in Article 9.2 and, in particular, without any warranty +as to its commercial value, its secured, safe, innovative or relevant +nature. + +Specifically, the Licensor does not warrant that the Software is free +from any error, that it will operate without interruption, that it will +be compatible with the Licensee's own equipment and software +configuration, nor that it will meet the Licensee's requirements. + +9.4 The Licensor does not either expressly or tacitly warrant that the +Software does not infringe any third party intellectual property right +relating to a patent, software or any other property right. Therefore, +the Licensor disclaims any and all liability towards the Licensee +arising out of any or all proceedings for infringement that may be +instituted in respect of the use, modification and redistribution of the +Software. Nevertheless, should such proceedings be instituted against +the Licensee, the Licensor shall provide it with technical and legal +assistance for its defense. Such technical and legal assistance shall be +decided on a case-by-case basis between the relevant Licensor and the +Licensee pursuant to a memorandum of understanding. The Licensor +disclaims any and all liability as regards the Licensee's use of the +name of the Software. No warranty is given as regards the existence of +prior rights over the name of the Software or as regards the existence +of a trademark. + + + Article 10 - TERMINATION + +10.1 In the event of a breach by the Licensee of its obligations +hereunder, the Licensor may automatically terminate this Agreement +thirty (30) days after notice has been sent to the Licensee and has +remained ineffective. + +10.2 A Licensee whose Agreement is terminated shall no longer be +authorized to use, modify or distribute the Software. However, any +licenses that it may have granted prior to termination of the Agreement +shall remain valid subject to their having been granted in compliance +with the terms and conditions hereof. + + + Article 11 - MISCELLANEOUS + + + 11.1 EXCUSABLE EVENTS + +Neither Party shall be liable for any or all delay, or failure to +perform the Agreement, that may be attributable to an event of force +majeure, an act of God or an outside cause, such as defective +functioning or interruptions of the electricity or telecommunications +networks, network paralysis following a virus attack, intervention by +government authorities, natural disasters, water damage, earthquakes, +fire, explosions, strikes and labor unrest, war, etc. + +11.2 Any failure by either Party, on one or more occasions, to invoke +one or more of the provisions hereof, shall under no circumstances be +interpreted as being a waiver by the interested Party of its right to +invoke said provision(s) subsequently. + +11.3 The Agreement cancels and replaces any or all previous agreements, +whether written or oral, between the Parties and having the same +purpose, and constitutes the entirety of the agreement between said +Parties concerning said purpose. No supplement or modification to the +terms and conditions hereof shall be effective as between the Parties +unless it is made in writing and signed by their duly authorized +representatives. + +11.4 In the event that one or more of the provisions hereof were to +conflict with a current or future applicable act or legislative text, +said act or legislative text shall prevail, and the Parties shall make +the necessary amendments so as to comply with said act or legislative +text. All other provisions shall remain effective. Similarly, invalidity +of a provision of the Agreement, for any reason whatsoever, shall not +cause the Agreement as a whole to be invalid. + + + 11.5 LANGUAGE + +The Agreement is drafted in both French and English and both versions +are deemed authentic. + + + Article 12 - NEW VERSIONS OF THE AGREEMENT + +12.1 Any person is authorized to duplicate and distribute copies of this +Agreement. + +12.2 So as to ensure coherence, the wording of this Agreement is +protected and may only be modified by the authors of the License, who +reserve the right to periodically publish updates or new versions of the +Agreement, each with a separate number. These subsequent versions may +address new issues encountered by Free Software. + +12.3 Any Software distributed under a given version of the Agreement may +only be subsequently distributed under the same version of the Agreement +or a subsequent version. + + + Article 13 - GOVERNING LAW AND JURISDICTION + +13.1 The Agreement is governed by French law. The Parties agree to +endeavor to seek an amicable solution to any disagreements or disputes +that may arise during the performance of the Agreement. + +13.2 Failing an amicable solution within two (2) months as from their +occurrence, and unless emergency proceedings are necessary, the +disagreements or disputes shall be referred to the Paris Courts having +jurisdiction, by the more diligent Party. + + +Version 1.0 dated 2006-09-05. +<----- End of the COPYING file in contrib/knem/ ------> + +The Debian packaging is © 2009, Lucas Nussbaum +and is licensed under the GPL Version 3, see `/usr/share/common-licenses/GPL-3'. + --- mpich2-1.2.1.1.orig/debian/libmpich2-1.2.install +++ mpich2-1.2.1.1/debian/libmpich2-1.2.install @@ -0,0 +1,4 @@ +usr/lib/libmpich.so.1.2 +usr/lib/libfmpich.so.1.2 +usr/lib/libmpichcxx.so.1.2 +usr/lib/libmpichf90.so.1.2 --- mpich2-1.2.1.1.orig/debian/compat +++ mpich2-1.2.1.1/debian/compat @@ -0,0 +1 @@ +7 --- mpich2-1.2.1.1.orig/debian/mpich2.install +++ mpich2-1.2.1.1/debian/mpich2.install @@ -0,0 +1,5 @@ +usr/bin/*py /usr/share/mpich2/ +usr/bin/mpdroot +usr/bin/pmi_proxy +usr/bin/mpiexec.gforker +usr/bin/mpiexec.hydra --- mpich2-1.2.1.1.orig/debian/run-tests.bash +++ mpich2-1.2.1.1/debian/run-tests.bash @@ -0,0 +1,18 @@ +#!/bin/bash + +set -x +set -e + +if [ $(id -u) -eq 0 ]; then + echo "Building as root, cant run test suite" + exit 0 +fi + +cd test/mpi +export LD_LIBRARY_PATH=$(pwd)/../../lib +./configure --with-mpi=$(pwd)/../../ +echo MPD_SECRETWORD=secretword > .mpd.conf +chmod 600 .mpd.conf +MPD_CONF_FILE=$(pwd)/.mpd.conf ../../bin/mpdboot +MPD_CONF_FILE=$(pwd)/.mpd.conf RUNTESTS_VERBOSE=1 make testing || true +MPD_CONF_FILE=$(pwd)/.mpd.conf ../../bin/mpdallexit --- mpich2-1.2.1.1.orig/debian/rules +++ mpich2-1.2.1.1/debian/rules @@ -0,0 +1,74 @@ +#! /usr/bin/make -f + +include /usr/share/cdbs/1/rules/debhelper.mk +include /usr/share/cdbs/1/class/autotools.mk +include /usr/share/cdbs/1/rules/utils.mk +include /usr/share/cdbs/1/rules/patchsys-quilt.mk + + +# Uncomment this to turn on verbose mode. +export DH_VERBOSE=1 + +DEB_CONFIGURE_EXTRA_FLAGS := \ + --enable-sharedlibs=gcc \ + --prefix=/usr \ + --enable-f90 \ + --sysconfdir=/etc/mpich2 \ + --includedir=/usr/include/mpich2 \ + --docdir=/usr/share/doc/mpich2 + +# On sparc and sh4, OPA isn't available, so we need to fallback to +# emulation mode. There's a performance penalty, unfortunately. +ifneq (,$(findstring $(DEB_HOST_GNU_CPU),sparc sh4)) + DEB_CONFIGURE_EXTRA_FLAGS += --with-atomic-primitives=no +endif + +DEB_MAKE_CLEAN_TARGET := distclean + +clean:: + rm -f src/binding/f90/libmpichf90.la bin/mpic++ bin/parkill src/mpe2/src/slog2sdk/awt_color.jar src/mpe2/src/slog2sdk/share/logfiles/fpilog.clog src/mpe2/src/slog2sdk/share/logfiles/fpilog.slog2 + +# run MPI test suite +# Custom rules based on the makefile CDBS class +ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS))) +common-build-arch common-build-indep:: debian/stamp-makefile-testing +debian/stamp-makefile-testing: debian/stamp-makefile-build + bash debian/run-tests.bash + touch $@ + +makefile-clean:: + rm -f debian/stamp-makefile-testing +endif + +# do some post-installation renamings +binary-install/libmpich2-dev:: + for i in mpicc mpicxx mpif77 mpif90; do \ + (cd debian/libmpich2-dev/usr/bin/ && mv $$i $$i.mpich2); \ + (cd debian/libmpich2-dev/usr/share/man/man1/ && mv $$i.1 $$i.mpich2.1);\ + done + rm -f debian/libmpich2-dev/usr/bin/mpic++ debian/libmpich2-dev/usr/share/man/man1/mpic++.1 + dh_link -plibmpich2-dev /usr/bin/mpicxx.mpich2 /usr/bin/mpic++.mpich2 + dh_link -plibmpich2-dev /usr/share/man/man1/mpicxx.mpich2.1 /usr/share/man/man1/mpic++.mpich2.1 + +binary-install/mpich2:: + dh_pysupport -pmpich2 + for i in mpd mpdallexit mpdboot mpdcheck mpdcleanup mpdexit \ + mpdgdbdrv mpdhelp mpdkilljob mpdlistjobs mpdman \ + mpdringtest mpdrun mpdsigjobs mpdtrace; do \ + dh_link -pmpich2 /usr/share/mpich2/$$i.py /usr/bin/$$i ;\ + done + for i in mpiexec mpirun; do \ + dh_link -pmpich2 /usr/share/mpich2/$$i.py /usr/bin/$$i.mpich2 ;\ + done + mv debian/mpich2/usr/share/man/man1/MPI.1 debian/mpich2/usr/share/man/man1/MPI.mpich2.1 + mv debian/mpich2/usr/share/man/man1/mpiexec.1 debian/mpich2/usr/share/man/man1/mpiexec.mpich2.1 + dh_link -pmpich2 /usr/share/man/man1/mpiexec.mpich2.1 /usr/share/man/man1/mpirun.mpich2.1 + +list-missing-mine: + (cd debian/tmp && find . -type f -exec md5sum {} \+ | grep -v '/DEBIAN/') > debian/tmp-files + (for package in $(DEB_ALL_PACKAGES); do \ + (cd debian/$$package && find . -type f -exec md5sum {} \+ | grep -v '/DEBIAN/'); done) > debian/pkg-files + awk '{print $$1}' debian/tmp-files > debian/tmp-files-md5 + awk '{print $$1}' debian/pkg-files > debian/pkg-files-md5 + for i in $$(combine debian/tmp-files-md5 not debian/pkg-files-md5); do \ + grep $$i debian/tmp-files; done --- mpich2-1.2.1.1.orig/debian/watch +++ mpich2-1.2.1.1/debian/watch @@ -0,0 +1,5 @@ +# Compulsory line, this is a version 3 file +version=3 +opts="dversionmangle=s/\+dfsg\.\d+$//" \ +http://www.mcs.anl.gov/research/projects/mpich2/downloads/index.php?s=downloads \ +.*/mpich2-(.*)\.tar\.gz --- mpich2-1.2.1.1.orig/debian/libmpich2-dev.prerm +++ mpich2-1.2.1.1/debian/libmpich2-dev.prerm @@ -0,0 +1,11 @@ +#!/bin/sh + +set -e + +if [ "$1" != "upgrade" ]; then + update-alternatives --remove mpi /usr/include/mpich2 +fi + +#DEBHELPER# + +exit 0 --- mpich2-1.2.1.1.orig/debian/control +++ mpich2-1.2.1.1/debian/control @@ -0,0 +1,81 @@ +Source: mpich2 +Section: devel +Priority: extra +Maintainer: Debian Science Maintainers +Uploaders: Lucas Nussbaum +Build-Depends: debhelper (>= 7), cdbs, python, gfortran, txt2man, libxt-dev, x11proto-core-dev, default-jdk, python-support, quilt, procps +Standards-Version: 3.8.4 +Homepage: http://www.mcs.anl.gov/research/projects/mpich2/ +Vcs-Browser: http://git.debian.org/?p=debian-science/packages/mpich2.git;a=summary +Vcs-Git: git://git.debian.org/debian-science/packages/mpich2.git + +Package: mpich2 +Architecture: any +Depends: libmpich2-1.2 (= ${binary:Version}), ${python:Depends}, ${shlibs:Depends}, ${misc:Depends} +Recommends: libmpich2-dev (= ${binary:Version}) +Suggests: mpich2-doc (= ${source:Version}) +Conflicts: mpd +Description: Implementation of the MPI Message Passing Interface standard + MPICH2 is a high-performance and widely portable implementation of the + Message Passing Interface (MPI) standard (both MPI-1 and MPI-2). It + efficiently supports different computation and communication platforms + including commodity clusters, SMPs, massively parallel systems, and + high-speed networks. + . + This package includes the program binaries necessary to run MPICH2 programs. + +Package: mpich2-doc +Architecture: all +Section: doc +Depends: ${misc:Depends} +Conflicts: lam-mpidoc, lam4-dev, mpi-doc, openmpi-mpidoc, openmpi-doc +Description: Documentation for MPICH2 + MPICH2 is a high-performance and widely portable implementation of the + Message Passing Interface (MPI) standard (both MPI-1 and MPI-2). It + efficiently supports different computation and communication platforms + including commodity clusters, SMPs, massively parallel systems, and + high-speed networks. + . + This package includes the MPICH2 documentation. + +Package: libmpich2-1.2 +Architecture: any +Section: libs +Depends: ${shlibs:Depends}, ${misc:Depends} +Description: Shared libraries for MPICH2 + MPICH2 is a high-performance and widely portable implementation of the + Message Passing Interface (MPI) standard (both MPI-1 and MPI-2). It + efficiently supports different computation and communication platforms + including commodity clusters, SMPs, massively parallel systems, and + high-speed networks. + . + This package includes the MPICH2 shared libraries. + +Package: libmpich2-dev +Architecture: any +Section: libdevel +Depends: libmpich2-1.2 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends} +Recommends: mpich2 (= ${binary:Version}) +Description: Development files for MPICH2 + MPICH2 is a high-performance and widely portable implementation of the + Message Passing Interface (MPI) standard (both MPI-1 and MPI-2). It + efficiently supports different computation and communication platforms + including commodity clusters, SMPs, massively parallel systems, and + high-speed networks. + . + This package includes the MPICH2 headers and static libraries, as well + as the compiler wrappers needed to build MPICH2 programs. + +#Package: libmpe-mpich2-dev +#Architecture: any +#Section: libdevel +#Depends: mpich2 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends} +#Description: Analysis tools for MPICH2 programs +# This is an implementation of the Message-Passing Interface (MPI). The goals of +# MPICH2 are to provide an MPI implementation for important platforms, including +# clusters, SMPs, and massively parallel processors. It also provides a vehicle +# for MPI implementation research and for developing new and better parallel +# programming environments. +# . +# This package includes the MPE environment, which provides a complete suite of +# analysis tools for MPI programs based on port processing approach. --- mpich2-1.2.1.1.orig/debian/changelog +++ mpich2-1.2.1.1/debian/changelog @@ -0,0 +1,69 @@ +mpich2 (1.2.1.1-2) unstable; urgency=medium + + * Add patch no-rpath.patch: don't set rpath. Closes: #558960. + * Added slave alternatives symlinks for MPI FORTRAN libraries + (Closes: #563705). + + -- Lucas Nussbaum Fri, 19 Mar 2010 21:53:47 +0100 + +mpich2 (1.2.1.1-1) unstable; urgency=low + + * New upstream release. + * Support building on sh4. Closes: #565289. + * Fix documentation about alternatives. Closes: #568237. + * Standards-Version: 3.8.4. No changes needed. + + -- Lucas Nussbaum Wed, 24 Feb 2010 11:57:03 +0100 + +mpich2 (1.2.1-2) unstable; urgency=low + + * Remove bashism in postinst introduced in 1.2.1-1. (fixes piuparts failure) + + -- Lucas Nussbaum Sun, 29 Nov 2009 11:44:58 +0100 + +mpich2 (1.2.1-1) unstable; urgency=low + + * New upstream release. + * Fix alternatives: use the same alternatives as LAM, mpich and (from + recently) openmpi. See #522429 for discussion. + * Increase alternatives score to 40 (same as OpenMPI). + * Fix FTBFS on s390 by using -fPIC instead of -fpic. Closes: #555943. + * Remove .py binary suffix in /usr/share/mpich2/*.py. + * Run the test suite, but ignore failures for now. + + -- Lucas Nussbaum Thu, 19 Nov 2009 11:37:30 -0600 + +mpich2 (1.2.1~rc1-1) unstable; urgency=low + + * Add Conflicts with mpd (the Music Player Daemon). While this is not the + "policy-correct" solution about this problem (which would be to rename + the binaries in one or the other package), it is the solution that makes + the most sense from the user's POV. Closes: #551932. + * mpich2: Suggest mpich2-doc instead of Recommending it. This avoids some + strange behaviour when installing mpich2 with LAM installed. + Closes: #551752. + * Fix build failure on sparc: build with --with-atomic-primitives=no. + * Update fPIC.patch: also fix FTBFS on sparc. + * Add sizeofOPAptr-all.patch: fix FTBFS on powerpc. + * Run the test suite using "make testing" during build. Can be + disabled with DEB_BUILD_OPTIONS=nocheck if it takes too much time. + * New upstream release: + + Drop sizeofOPAptr-all.patch, was a backport from upstream. + + Drop fPIC.patch: fixed upstream. + + Adds manpages for mpd* + + -- Lucas Nussbaum Wed, 11 Nov 2009 13:34:22 +0100 + +mpich2 (1.2-2) unstable; urgency=low + + * Upload to unstable. (Actually, 1.2-1 was already uploaded to unstable) + * Use the quilt patch system. + * Add fPIC.patch: build with -fPIC instead of -fpic (fix FTBFS on s390). + + -- Lucas Nussbaum Mon, 19 Oct 2009 10:44:01 +0200 + +mpich2 (1.2-1) experimental; urgency=low + + * Initial packaging. Closes: #420638 + + -- Lucas Nussbaum Wed, 07 Oct 2009 23:11:42 +0200 --- mpich2-1.2.1.1.orig/debian/mpich2.prerm +++ mpich2-1.2.1.1/debian/mpich2.prerm @@ -0,0 +1,11 @@ +#!/bin/sh + +set -e + +if [ "$1" != "upgrade" ]; then + update-alternatives --remove mpirun /usr/bin/mpirun.mpich2 +fi + +#DEBHELPER# + +exit 0 --- mpich2-1.2.1.1.orig/debian/mpich2-doc.docs +++ mpich2-1.2.1.1/debian/mpich2-doc.docs @@ -0,0 +1,6 @@ +RELEASE_NOTES +debian/tmp/usr/share/doc/mpich2/user.pdf +debian/tmp/usr/share/doc/mpich2/install.pdf +debian/tmp/usr/share/doc/mpich2/smpd_pmi.pdf +debian/tmp/usr/share/doc/mpich2/logging.pdf +debian/tmp/usr/share/doc/mpich2/www* --- mpich2-1.2.1.1.orig/debian/mpich2-doc.install +++ mpich2-1.2.1.1/debian/mpich2-doc.install @@ -0,0 +1 @@ +usr/share/man/man3/* --- mpich2-1.2.1.1.orig/debian/patches/no-rpath.patch +++ mpich2-1.2.1.1/debian/patches/no-rpath.patch @@ -0,0 +1,14 @@ +Backported from upstream changeset 6336 +http://trac.mcs.anl.gov/projects/mpich2/changeset/6336 + +--- a/configure ++++ b/configure +@@ -14717,7 +14717,7 @@ $as_echo "$as_me: error: Neither -fPIC n + fi + #C_LINKPATH_SHL="-Wl,-rpath -Wl," + # More recent versions allow multiple args, separated by commas +- C_LINKPATH_SHL="-Wl,-rpath," ++ C_LINKPATH_SHL="" + SHLIB_EXT=so + # We need to test that this isn't osx. The following is a + # simple hack --- mpich2-1.2.1.1.orig/debian/patches/series +++ mpich2-1.2.1.1/debian/patches/series @@ -0,0 +1,3 @@ +fPIC.patch +binaries-without-suffix.patch +no-rpath.patch --- mpich2-1.2.1.1.orig/debian/patches/fPIC.patch +++ mpich2-1.2.1.1/debian/patches/fPIC.patch @@ -0,0 +1,218 @@ +From: Lucas Nussbaum +Subject: Use -fPIC instead of -fpic + +-fPIC is required on some architectures (like s390 or sparc). + +This patch is dumb. We just hack configure to use -fPIC where -fpic is used. + +Origin: vendor +Forwarded: yes +Bug: https://trac.mcs.anl.gov/projects/mpich2/ticket/909 + +diff -u mpich2-1.2.1/debian/mpich2.postinst mpich2-1.2.1/debian/mpich2.postinst +--- mpich2-1.2.1.orig/configure ++++ mpich2-1.2.1/configure +@@ -10322,24 +10322,24 @@ + # if the compiler allows it (e.g., building with gcc but + # a different Fortran compiler. Another option is to + # *require* g77. +- { $as_echo "$as_me:$LINENO: checking whether $F77 allows -shared -fpic" >&5 +-$as_echo_n "checking whether $F77 allows -shared -fpic... " >&6; } ++ { $as_echo "$as_me:$LINENO: checking whether $F77 allows -shared -fPIC" >&5 ++$as_echo_n "checking whether $F77 allows -shared -fPIC... " >&6; } + rm -f conftest.f + cat > conftest.f </dev/null 2>&1 ; then +- FC_SHL="$F77 -shared -fpic" ++ if $F77 -shared -fPIC -o conftest conftest.f >/dev/null 2>&1 ; then ++ FC_SHL="$F77 -shared -fPIC" + { $as_echo "$as_me:$LINENO: result: yes" >&5 + $as_echo "yes" >&6; } + else + { $as_echo "$as_me:$LINENO: result: no" >&5 + $as_echo "no" >&6; } +- { $as_echo "$as_me:$LINENO: checking whether $F77 allows -fpic" >&5 +-$as_echo_n "checking whether $F77 allows -fpic... " >&6; } +- if $F77 -fpic -o conftest conftest.f >/dev/null 2>&1 ; then +- FC_SHL="$F77 -fpic" ++ { $as_echo "$as_me:$LINENO: checking whether $F77 allows -fPIC" >&5 ++$as_echo_n "checking whether $F77 allows -fPIC... " >&6; } ++ if $F77 -fPIC -o conftest conftest.f >/dev/null 2>&1 ; then ++ FC_SHL="$F77 -fPIC" + { $as_echo "$as_me:$LINENO: result: yes" >&5 + $as_echo "yes" >&6; } + else +@@ -11509,24 +11509,24 @@ + gcc) + if test "$pac_cv_f90_vendor" = gnu -o "$F90" = "g95" ; then + # If we have the GNU Fortran 95 compiler (untested) +- F90_SHL="$F90 -shared -fpic" ++ F90_SHL="$F90 -shared -fPIC" + F90_LINKPATH_SHL="-Wl,-rpath -Wl," + else + case "$pac_cv_f90_vendor" in + absoft) +- F90_SHL="$F90 -fpic" ++ F90_SHL="$F90 -fPIC" + F90_LINKPATH_SHL="-X -rpath -X " + ;; + + intel) + # Intel implements the GNU options +- F90_SHL="$F90 -shared -fpic" ++ F90_SHL="$F90 -shared -fPIC" + F90_LINKPATH_SHL="-Wl,-rpath -Wl," + ;; + + pgi) + # Portland Group implements the GNU options +- F90_SHL="$F90 -shared -fpic" ++ F90_SHL="$F90 -shared -fPIC" + F90_LINKPATH_SHL="-Wl,-rpath -Wl," + ;; + +@@ -12621,7 +12621,7 @@ + ;; + gcc) + # Assume that the compiler is g++ if gcc style shared libraries chosen +- CXX_SHL="$CXX -shared -fpic" ++ CXX_SHL="$CXX -shared -fPIC" + CXX_LINKPATH_SHL="-Wl,-rpath -Wl," + ;; + cygwin|cygwin-gcc) +@@ -14573,10 +14573,10 @@ + #C_LINK_SHL='${CC} -shared -Wl,-h,' + # May need -fPIC . Test to see which one works. + +-{ $as_echo "$as_me:$LINENO: checking whether C compiler accepts option -fpic" >&5 +-$as_echo_n "checking whether C compiler accepts option -fpic... " >&6; } ++{ $as_echo "$as_me:$LINENO: checking whether C compiler accepts option -fPIC" >&5 ++$as_echo_n "checking whether C compiler accepts option -fPIC... " >&6; } + pccco_save_CFLAGS="$CFLAGS" +-CFLAGS="-fpic $CFLAGS" ++CFLAGS="-fPIC $CFLAGS" + rm -f conftest.out + pac_success=no + # conftest3.c has an invalid prototype to ensure we generate warnings +@@ -14589,8 +14589,8 @@ + if diff -b conftest.out conftest.bas >/dev/null 2>&1 ; then + { $as_echo "$as_me:$LINENO: result: yes" >&5 + $as_echo "yes" >&6; } +- { $as_echo "$as_me:$LINENO: checking whether routines compiled with -fpic can be linked with ones compiled without -fpic" >&5 +-$as_echo_n "checking whether routines compiled with -fpic can be linked with ones compiled without -fpic... " >&6; } ++ { $as_echo "$as_me:$LINENO: checking whether routines compiled with -fPIC can be linked with ones compiled without -fPIC" >&5 ++$as_echo_n "checking whether routines compiled with -fPIC can be linked with ones compiled without -fPIC... " >&6; } + rm -f conftest.out + rm -f conftest.bas + if ${CC-cc} -c $pccco_save_CFLAGS $CPPFLAGS conftest2.c >conftest2.out 2>&1 ; then +@@ -14627,18 +14627,18 @@ + if test "$pac_success" = yes ; then + { $as_echo "$as_me:$LINENO: result: yes" >&5 + $as_echo "yes" >&6; } +- fpic_ok=yes ++ fPIC_ok=yes + else + { $as_echo "$as_me:$LINENO: result: no" >&5 + $as_echo "no" >&6; } + if test -s conftest.out ; then cat conftest.out >&5 ; fi +- fpic_ok=no ++ fPIC_ok=no + fi + # This is needed for Mac OSX 10.5 + rm -rf conftest.dSYM + rm -f conftest* + +- if test "$fpic_ok" != yes ; then ++ if test "$fPIC_ok" != yes ; then + + { $as_echo "$as_me:$LINENO: checking whether C compiler accepts option -fPIC" >&5 + $as_echo_n "checking whether C compiler accepts option -fPIC... " >&6; } +@@ -14706,14 +14706,14 @@ + rm -f conftest* + + if test "$fPIC_ok" != yes ; then +- { { $as_echo "$as_me:$LINENO: error: Neither -fpic nor -fPIC accepted by $CC" >&5 +-$as_echo "$as_me: error: Neither -fpic nor -fPIC accepted by $CC" >&2;} ++ { { $as_echo "$as_me:$LINENO: error: Neither -fPIC nor -fPIC accepted by $CC" >&5 ++$as_echo "$as_me: error: Neither -fPIC nor -fPIC accepted by $CC" >&2;} + { (exit 1); exit 1; }; } + else + CC_SHL='${CC} -fPIC' + fi + else +- CC_SHL='${CC} -fpic' ++ CC_SHL='${CC} -fPIC' + fi + #C_LINKPATH_SHL="-Wl,-rpath -Wl," + # More recent versions allow multiple args, separated by commas +@@ -15038,12 +15038,12 @@ + # For example, include the libname as ${LIBNAME_SHL} + #C_LINK_SHL='${CC} -shared -Wl,-h,' + pac_cc_sharedlibs='gcc -shared' +- # Make sure we select the correct fpic option ++ # Make sure we select the correct fPIC option + +-{ $as_echo "$as_me:$LINENO: checking whether C compiler accepts option -fpic" >&5 +-$as_echo_n "checking whether C compiler accepts option -fpic... " >&6; } ++{ $as_echo "$as_me:$LINENO: checking whether C compiler accepts option -fPIC" >&5 ++$as_echo_n "checking whether C compiler accepts option -fPIC... " >&6; } + pccco_save_CFLAGS="$CFLAGS" +-CFLAGS="-fpic $CFLAGS" ++CFLAGS="-fPIC $CFLAGS" + rm -f conftest.out + pac_success=no + # conftest3.c has an invalid prototype to ensure we generate warnings +@@ -15056,8 +15056,8 @@ + if diff -b conftest.out conftest.bas >/dev/null 2>&1 ; then + { $as_echo "$as_me:$LINENO: result: yes" >&5 + $as_echo "yes" >&6; } +- { $as_echo "$as_me:$LINENO: checking whether routines compiled with -fpic can be linked with ones compiled without -fpic" >&5 +-$as_echo_n "checking whether routines compiled with -fpic can be linked with ones compiled without -fpic... " >&6; } ++ { $as_echo "$as_me:$LINENO: checking whether routines compiled with -fPIC can be linked with ones compiled without -fPIC" >&5 ++$as_echo_n "checking whether routines compiled with -fPIC can be linked with ones compiled without -fPIC... " >&6; } + rm -f conftest.out + rm -f conftest.bas + if ${CC-cc} -c $pccco_save_CFLAGS $CPPFLAGS conftest2.c >conftest2.out 2>&1 ; then +@@ -15094,18 +15094,18 @@ + if test "$pac_success" = yes ; then + { $as_echo "$as_me:$LINENO: result: yes" >&5 + $as_echo "yes" >&6; } +- fpic_ok=yes ++ fPIC_ok=yes + else + { $as_echo "$as_me:$LINENO: result: no" >&5 + $as_echo "no" >&6; } + if test -s conftest.out ; then cat conftest.out >&5 ; fi +- fpic_ok=no ++ fPIC_ok=no + fi + # This is needed for Mac OSX 10.5 + rm -rf conftest.dSYM + rm -f conftest* + +- if test "$fpic_ok" != yes ; then ++ if test "$fPIC_ok" != yes ; then + + { $as_echo "$as_me:$LINENO: checking whether C compiler accepts option -fPIC" >&5 + $as_echo_n "checking whether C compiler accepts option -fPIC... " >&6; } +@@ -15173,14 +15173,14 @@ + rm -f conftest* + + if test "$fPIC_ok" != yes ; then +- { { $as_echo "$as_me:$LINENO: error: Neither -fpic nor -fPIC accepted by $CC" >&5 +-$as_echo "$as_me: error: Neither -fpic nor -fPIC accepted by $CC" >&2;} ++ { { $as_echo "$as_me:$LINENO: error: Neither -fPIC nor -fPIC accepted by $CC" >&5 ++$as_echo "$as_me: error: Neither -fPIC nor -fPIC accepted by $CC" >&2;} + { (exit 1); exit 1; }; } + else + pac_cc_sharedlibs="$pac_cc_sharedlibs -fPIC" + fi + else +- pac_cc_sharedlibs="$pac_cc_sharedlibs -fpic" ++ pac_cc_sharedlibs="$pac_cc_sharedlibs -fPIC" + fi + pac_clink_sharedlibs='gcc -shared' + pac_type_sharedlibs=gcc --- mpich2-1.2.1.1.orig/debian/patches/binaries-without-suffix.patch +++ mpich2-1.2.1.1/debian/patches/binaries-without-suffix.patch @@ -0,0 +1,151 @@ +From: Lucas Nussbaum +Subject: Remove .py suffix from binaries + +In Debian, we have a policy of not using language-specific suffixes in +/usr/bin. As a result, mpd* binaries are in /usr/share/mpich2, and +symlinks without .py are put in /usr/bin. But as the result, mpd* look for +the wrong filename in /usr/bin. + +Origin: vendor +Forwarded: yes +--- a/src/pm/mpd/mpd.py ++++ b/src/pm/mpd/mpd.py +@@ -1607,7 +1607,7 @@ class MPD(object): + # python_executable = '\Python24\python.exe' + python_executable = 'python2.4' + fullDirName = man_env['MPDMAN_FULLPATHDIR'] +- manCmd = os.path.join(fullDirName,'mpdman.py') ++ manCmd = os.path.join(fullDirName,'mpdman') + runner = subprocess.Popen([python_executable,'-u',manCmd], # only one 'python' arg + bufsize=0, + env=man_env, +--- a/src/pm/mpd/mpdboot.py ++++ b/src/pm/mpd/mpdboot.py +@@ -76,7 +76,7 @@ def mpdboot(): + fullDirName = path.abspath(path.split(argv[0])[0]) + rshCmd = 'ssh' + user = mpd_get_my_username() +- mpdCmd = path.join(fullDirName,'mpd.py') ++ mpdCmd = path.join(fullDirName,'mpd') + hostsFilename = 'mpd.hosts' + totalnumToStart = 1 # may get chgd below + debug = 0 +@@ -268,7 +268,7 @@ def mpdboot(): + + try: + # stop current (if any) mpds; ignore the output +- getoutput('%s/mpdallexit.py' % (fullDirName)) ++ getoutput('%s/mpdallexit' % (fullDirName)) + if verbose or debug: + print 'running mpdallexit on %s' % (myHost) + except: +@@ -407,20 +407,20 @@ def handle_mpd_output(fd,fd2idx,hostsAnd + (host,msg) ) + tempOut = tempSock.recv(1000) + print tempOut +- try: getoutput('%s/mpdallexit.py' % (fullDirName)) ++ try: getoutput('%s/mpdallexit' % (fullDirName)) + except: pass + exit(-1) + tempSock.close() + else: + mpd_print(1,'failed to connect to mpd on %s' % (host) ) +- try: getoutput('%s/mpdallexit.py' % (fullDirName)) ++ try: getoutput('%s/mpdallexit' % (fullDirName)) + except: pass + exit(-1) + else: + mpd_print(1,'from mpd on %s, invalid port info:' % (host) ) + print port + print fd.read() +- try: getoutput('%s/mpdallexit.py' % (fullDirName)) ++ try: getoutput('%s/mpdallexit' % (fullDirName)) + except: pass + exit(-1) + if verbose: +--- a/src/pm/mpd/mpdcheck.py ++++ b/src/pm/mpd/mpdcheck.py +@@ -461,7 +461,7 @@ if __name__ == '__main__': # so I can + + # see if we can run mpdcheck on remote hosts + for host in hostsFromFile: +- cmd1 = path.join(fullDirName,'mpdcheck.py') + ' -s' ++ cmd1 = path.join(fullDirName,'mpdcheck') + ' -s' + if verbose: + print 'starting server: %s' % (cmd1) + runner1 = Popen3(cmd1,1,0) +@@ -520,7 +520,7 @@ if __name__ == '__main__': # so I can + except: + pass + exit(-1) +- cmd2 = "ssh %s -x -n %s%smpdcheck.py -c %s %s" % (host,fullDirName,path.sep,fqhn1,port) ++ cmd2 = "ssh %s -x -n %s%smpdcheck -c %s %s" % (host,fullDirName,path.sep,fqhn1,port) + if verbose: + print 'starting client: %s' % (cmd2) + runner2 = Popen3(cmd2,1,0) +--- a/src/pm/mpd/mpdchkpyver.py ++++ b/src/pm/mpd/mpdchkpyver.py +@@ -37,7 +37,7 @@ if __name__ == '__main__': + print "mpdchkpyver: your python version must be >= 2.2 ; current version is:", vinfo + exit(-1) + if len(argv) > 1: +- mpdpgm = argv[1] + '.py' ++ mpdpgm = argv[1] + # print "CHKPYVER: PGM=:%s: ARGV[1:]=:%s:" % (mpdpgm,argv[1:]) + try: + execvpe(mpdpgm,argv[1:],environ) # client +--- a/src/pm/mpd/mpdman.py ++++ b/src/pm/mpd/mpdman.py +@@ -1485,7 +1485,7 @@ class MPDMan(object): + mpd_print(0000, 'execing clientPgm=:%s:' % (self.clientPgm) ) + if self.gdb: + fullDirName = os.environ['MPDMAN_FULLPATHDIR'] +- gdbdrv = os.path.join(fullDirName,'mpdgdbdrv.py') ++ gdbdrv = os.path.join(fullDirName,'mpdgdbdrv') + if not os.access(gdbdrv,os.X_OK): + print 'mpdman: cannot execute mpdgdbdrv %s' % gdbdrv + sys.exit(0); +@@ -1524,7 +1524,7 @@ class MPDMan(object): + # python_executable = '\Python24\python.exe' + python_executable = 'python2.4' + fullDirName = os.environ['MPDMAN_FULLPATHDIR'] +- mpdwrapcli = os.path.join(fullDirName,'mpdwrapcli.py') ++ mpdwrapcli = os.path.join(fullDirName,'mpdwrapcli') + wrapCmdAndArgs = [ mpdwrapcli, str(tempListenPort), + self.clientPgm, self.clientPgm ] + self.clientPgmArgs + cli_env.update(os.environ) ###### RMB: MAY NEED VARS OTHER THAN PATH ????? +--- a/src/pm/mpd/newboot.py ++++ b/src/pm/mpd/newboot.py +@@ -64,7 +64,7 @@ def mpdboot(): + fullDirName = path.abspath(path.split(argv[0])[0]) + rshCmd = 'ssh' + user = mpd_get_my_username() +- mpdCmd = path.join(fullDirName,'mpd.py') ++ mpdCmd = path.join(fullDirName,'mpd') + hostsFilename = 'mpd.hosts' + totalnumToStart = 0 + debug = 0 +@@ -345,20 +345,20 @@ def handle_mpd_output(fd,fd2idx,hostsAnd + mpd_print(1,'failed to handshake mpd on %s; recvd output=%s' % (host,msg) ) + tempOut = tempSock.recv(1000) + print tempOut +- try: getoutput('%s/mpdallexit.py' % (fullDirName)) ++ try: getoutput('%s/mpdallexit' % (fullDirName)) + except: pass + exit(-1) + tempSock.close() + else: + mpd_print(1,'failed to connect to mpd on %s' % (host) ) +- try: getoutput('%s/mpdallexit.py' % (fullDirName)) ++ try: getoutput('%s/mpdallexit' % (fullDirName)) + except: pass + exit(-1) + else: + mpd_print(1,'from mpd on %s, invalid port info:' % (host) ) + print port + print fd.read() +- try: getoutput('%s/mpdallexit.py' % (fullDirName)) ++ try: getoutput('%s/mpdallexit' % (fullDirName)) + except: pass + exit(-1) + if verbose: --- mpich2-1.2.1.1.orig/debian/man.Attic/mpd.1 +++ mpich2-1.2.1.1/debian/man.Attic/mpd.1 @@ -0,0 +1,78 @@ +.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.36. +.TH MPD "1" "September 2009" "mpd" "User Commands" +.SH NAME +mpd \- manual page for mpd daemon +.SH DESCRIPTION +usage: mpd [\-\-host= \fB\-\-port=\fR] [\-\-noconsole] +.IP +[\-\-trace] [\-\-echo] [\-\-daemon] [\-\-bulletproof] \fB\-\-ncpus=\fR +[\-\-ifhn=] [\-\-listenport=] +[\-\-pid=] \fB\-\-tmpdir=\fR] [\-zc] [\-\-debug] +.PP +Some long parameter names may be abbreviated to their first letters by using +.IP +only one hyphen and no equal sign: +.IP +mpd \fB\-h\fR donner \fB\-p\fR 4268 \fB\-n\fR +.IP +is equivalent to +.IP +mpd \fB\-\-host\fR=\fImagpie\fR \fB\-\-port\fR=\fI4268\fR \fB\-\-noconsole\fR +.PP +\fB\-\-host\fR and \fB\-\-port\fR must be specified together; they tell the new mpd where +.TP +to enter an existing ring; +if they are omitted, the new mpd forms a +.IP +stand\-alone ring that other mpds may enter later +.PP +\fB\-\-noconsole\fR is useful for running 2 mpds on the same machine; only one of +.IP +them will accept mpd commands +.PP +\fB\-\-trace\fR yields lots of traces thru mpd routines; currently too verbose +\fB\-\-debug\fR turns on some debugging prints; currently not verbose enough +\fB\-\-echo\fR causes the mpd echo its listener port by which other mpds may connect +\fB\-\-daemon\fR causes mpd to run backgrounded, with no controlling tty +\fB\-\-bulletproof\fR says to turn bulletproofing on (experimental) +\fB\-\-ncpus\fR indicates how many cpus are on the local host; used for starting processes +\fB\-\-ifhn\fR specifies an alternate interface hostname for the host this mpd is running on; +.IP +e.g. may be used to specify the alias for an interface other than default +.PP +\fB\-\-listenport\fR specifies a port for this mpd to listen on; by default it will +.IP +acquire one from the system +.PP +\fB\-\-conlistenport\fR specifies a port for this mpd to listen on for console +.IP +connections (only used when employing inet socket for console); by default it +will acquire one from the system +.PP +\fB\-\-pid\fR=\fIfilename\fR writes the mpd pid into the specified file, or \fB\-\-pid\fR alone +.IP +writes it into /var/run/mpd.pid +.PP +\fB\-\-tmpdir\fR=\fItmpdirname\fR where mpd places temporary sockets, etc. +\fB\-zc\fR is a purely EXPERIMENTAL option right now used to investigate zeroconf +.IP +networking; it can be used to allow mpds to discover each other locally +using multicast DNS; its usage may change over time +Currently, \fB\-zc\fR is specified like this: \fB\-zc\fR N +where N specifies a 'level' in a startup set of mpds. The first mpd in a ring +must have 1 and it will establish a ring of one mpd. Subsequent mpds can specify +\fB\-zc\fR 2 and will hook into the ring via the one at level 1. Except for level 1, new +mpds enter the ring via an mpd at level\-1. +.PP +A file named .mpd.conf file must be present in the user's home directory +.IP +with read and write access only for the user, and must contain at least +a line with MPD_SECRETWORD= +.PP +To run mpd as root, install it while root and instead of a .mpd.conf file +use mpd.conf (no leading dot) in the /etc directory.' +.SH AUTHOR +mpd was written by The MPICH2 Team. +.PP +This manual page was written by Muammar El Khatib , +for the Debian project (but may be used by others). --- mpich2-1.2.1.1.orig/debian/man.Attic/clog2_print.1 +++ mpich2-1.2.1.1/debian/man.Attic/clog2_print.1 @@ -0,0 +1,16 @@ +.TH clog2_print 1 "21 Mar 2005" "" "MPI" +.SH NAME +clog2_print \- prints out the contents of a clog file +.SH SYNOPSIS +.B clog2_print [ +.I clogfilename +.B ] + +.SH DESCRIPTION +.B clog2_print +dumps the contents of a clog file out to stdout. +.SH AUTHOR +This manpage has been written by Zach Lowry , modified from +the page written by Junichi Uekawa for Debian GNU/Linux +.SH "SEE ALSO" +mpicc(1), mpicxx(1), mpif77(1), mpirun(1), "MPICH2 user's guide". --- mpich2-1.2.1.1.orig/debian/man.Attic/mpich2version.1 +++ mpich2-1.2.1.1/debian/man.Attic/mpich2version.1 @@ -0,0 +1,15 @@ +.TH mpich2version 1 "21 Mar 2005" "" "MPI" +.SH NAME +mpich2version \- prints information about installed version of mpich2 +.SH SYNOPSIS +.B mpich2version + +.SH DESCRIPTION +.B mpich2version +Prints version information such as upstream version, configure options, build +date, etc. +.SH AUTHOR +This manpage has been written by Zach Lowry . Modified from +the page written by Adam Powell for Debian GNU/Linux +.SH "SEE ALSO" +mpirun(1), "MPICH2 user's guide". --- mpich2-1.2.1.1.orig/debian/man.Attic/mpdcheck.1 +++ mpich2-1.2.1.1/debian/man.Attic/mpdcheck.1 @@ -0,0 +1,64 @@ +.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.36. +.TH MPDCHECK "1" "September 2009" "mpdcheck" "User Commands" +.SH NAME +unrecognized \- manual page for mpdcheck command +.SH DESCRIPTION +mpdcheck +.PP +This script is a work in progress and may change frequently as we work +with users and gain additional insights into how to improve it. +.PP +This script prints useful information about the host on which it runs. +It is here to help us help users detect problems with configurations of +their computers. For example, some computers are configured to think +of themselves simply as 'localhost' with 127.0.0.1 as the IP address. +This might present problems if a process on that computer wishes to +identify itself by host and port to a process on another computer. +The process on the other computer would try to contact 'localhost'. +.PP +If you are having problems running parallel jobs via mpd on one or more +hosts, you might try running this script once on each of those hosts. +.PP +Any output with *** at the beginning indicates a potential problem +that you may have to resolve before being able to run parallel jobs +via mpd. +.SS "For help:" +.IP +mpdcheck \fB\-h\fR (or \fB\-\-help\fR) +.IP +prints this message +.PP +In the following modes, the \fB\-v\fR (verbose) option provides info about what +mpdcheck is doing; the \fB\-l\fR (long messages) option causes long informational +messages to print in situations where problems are spotted. +.PP +The three major modes of operation for this program are: +.IP +mpdcheck +.IP +looks for config problems on 'this' host; prints as nec +.IP +mpdcheck \fB\-pc\fR +.IP +print config info about 'this' host, e.g. contents of /etc/hosts, etc. +.IP +mpdcheck \fB\-f\fR some_file [\-ssh] +.IP +prints info about 'this' host and locatability info about the ones +listed in some_file as well (note the file might be mpd.hosts); +the \fB\-ssh\fR option can be used in conjunction with the \fB\-f\fR option to +cause ssh tests to be run to each remote host +.IP +mpdcheck \fB\-s\fR +.IP +runs this program as a server on one host +.IP +mpdcheck \fB\-c\fR server_host server_port +.IP +runs a client on another (or same) host; connects to the specifed +host/port where you previously started the server +.SH AUTHOR +mpdcheck was written by The MPICH2 Team. +.PP +This manual page was written by Muammar El Khatib , +for the Debian project (but may be used by others). --- mpich2-1.2.1.1.orig/debian/man.Attic/mpdboot.1 +++ mpich2-1.2.1.1/debian/man.Attic/mpdboot.1 @@ -0,0 +1,139 @@ +.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.36. +.TH MPDBOOT: "1" "September 2009" "mpdboot" "User Commands" +.SH NAME +mpdboot: \- manual page for mpdboot command +.SH DESCRIPTION +usage: mpdboot \fB\-\-totalnum=\fR [\-\-file=] [\-\-help] \e +.TP +[\-\-rsh=] [\-\-user=] [\-\-mpd=] +\e +.TP +[\-\-loccons] [\-\-remcons] [\-\-shell] [\-\-verbose] [\-1] +[\-\-ncpus=] [\-\-ifhn=] [\-\-chkup] [\-\-chkuponly] [\-\-maxbranch=] +.IP +or, in short form, +.IP +mpdboot \fB\-n\fR n_to_start [\-f ] [\-h] [\-r ] [\-u ] \e +.TP +[\-m ] +\fB\-s\fR \fB\-v\fR [\-1] [\-c] +.PP +\fB\-\-totalnum\fR specifies the total number of mpds to start; at least +.IP +one mpd will be started locally, and others on the machines specified +by the file argument; by default, only one mpd per host will be +started even if the hostname occurs multiple times in the hosts file +.PP +\fB\-1\fR means remove the restriction of starting only one mpd per machine; +.IP +in this case, at most the first mpd on a host will have a console +.PP +\fB\-\-file\fR specifies the file of machines to start the rest of the mpds on; +.IP +it defaults to mpd.hosts +.PP +\fB\-\-mpd\fR specifies the full path name of mpd on the remote hosts if it is +.IP +not in your path +.PP +\fB\-\-rsh\fR specifies the name of the command used to start remote mpds; it +.IP +defaults to ssh; an alternative is rsh +.PP +\fB\-\-shell\fR says that the Bourne shell is your default for rsh' +\fB\-\-verbose\fR shows the ssh attempts as they occur; it does not provide +.IP +confirmation that the sshs were successful +.PP +\fB\-\-loccons\fR says you do not want a console available on local mpd(s) +\fB\-\-remcons\fR says you do not want consoles available on remote mpd(s) +\fB\-\-ncpus\fR indicates how many cpus you want to show for the local machine; +.IP +others are listed in the hosts file +.PP +\fB\-\-ifhn\fR indicates the interface hostname to use for the local mpd; others +.IP +may be specified in the hostsfile +.PP +\fB\-\-chkup\fR requests that mpdboot try to verify that the hosts in the host file +.IP +are up before attempting start mpds on any of them; it just checks the number +of hosts specified by \fB\-n\fR +.PP +\fB\-\-chkuponly\fR requests that mpdboot try to verify that the hosts in the host file +.IP +are up; it then terminates; it just checks the number of hosts specified by \fB\-n\fR +.PP +\fB\-\-maxbranch\fR indicates the maximum number of mpds to enter the ring under another; +.IP +the default is 4 +.PP +usage: mpdboot \fB\-\-totalnum=\fR [\-\-file=] [\-\-help] \e +.TP +[\-\-rsh=] [\-\-user=] [\-\-mpd=] +\e +.TP +[\-\-loccons] [\-\-remcons] [\-\-shell] [\-\-verbose] [\-1] +[\-\-ncpus=] [\-\-ifhn=] [\-\-chkup] [\-\-chkuponly] [\-\-maxbranch=] +.IP +or, in short form, +.IP +mpdboot \fB\-n\fR n_to_start [\-f ] [\-h] [\-r ] [\-u ] \e +.TP +[\-m ] +\fB\-s\fR \fB\-v\fR [\-1] [\-c] +.PP +\fB\-\-totalnum\fR specifies the total number of mpds to start; at least +.IP +one mpd will be started locally, and others on the machines specified +by the file argument; by default, only one mpd per host will be +started even if the hostname occurs multiple times in the hosts file +.PP +\fB\-1\fR means remove the restriction of starting only one mpd per machine; +.IP +in this case, at most the first mpd on a host will have a console +.PP +\fB\-\-file\fR specifies the file of machines to start the rest of the mpds on; +.IP +it defaults to mpd.hosts +.PP +\fB\-\-mpd\fR specifies the full path name of mpd on the remote hosts if it is +.IP +not in your path +.PP +\fB\-\-rsh\fR specifies the name of the command used to start remote mpds; it +.IP +defaults to ssh; an alternative is rsh +.PP +\fB\-\-shell\fR says that the Bourne shell is your default for rsh' +\fB\-\-verbose\fR shows the ssh attempts as they occur; it does not provide +.IP +confirmation that the sshs were successful +.PP +\fB\-\-loccons\fR says you do not want a console available on local mpd(s) +\fB\-\-remcons\fR says you do not want consoles available on remote mpd(s) +\fB\-\-ncpus\fR indicates how many cpus you want to show for the local machine; +.IP +others are listed in the hosts file +.PP +\fB\-\-ifhn\fR indicates the interface hostname to use for the local mpd; others +.IP +may be specified in the hostsfile +.PP +\fB\-\-chkup\fR requests that mpdboot try to verify that the hosts in the host file +.IP +are up before attempting start mpds on any of them; it just checks the number +of hosts specified by \fB\-n\fR +.PP +\fB\-\-chkuponly\fR requests that mpdboot try to verify that the hosts in the host file +.IP +are up; it then terminates; it just checks the number of hosts specified by \fB\-n\fR +.PP +\fB\-\-maxbranch\fR indicates the maximum number of mpds to enter the ring under another; +.IP +the default is 4 +.SH AUTHOR +mpdboot was written by The MPICH2 Team. +.PP +This manual page was written by Muammar El Khatib , +for the Debian project (but may be used by others). --- mpich2-1.2.1.1.orig/debian/man.Attic/mpigdb.1 +++ mpich2-1.2.1.1/debian/man.Attic/mpigdb.1 @@ -0,0 +1,17 @@ +.TH mpigdb 1 "21 Mar 2005" "" "mpd cmds" +.SH NAME +mpigdb \- debug a MPI program using mpd +.SH SYNOPSIS +.B mpigdb + +.SH DESCRIPTION +.B mpigdb +usage: +.TP +mpigdb -a jobid # to attach to a running job +.TP +mpigdb -n nprocs pgm [pgmars] # to use gdb on a new job + +.SH AUTHOR +This manpage has been written by Zach Lowry , modified from +the page written by Junichi Uekawa for Debian GNU/Linux