Re: [mpich-discuss] GFORTRAN on MinGW doesn't link to MPICH-2
Hello, Bland Thank you for your input, but 1.4.1p is exactly what I am using now, it should be recognized by the system, I believe. It is downloaded from http://www.mcs.anl.gov/research/projects/mpich2staging/goodell/downloads/ind... On Wed, Sep 17, 2014 at 10:45 AM, <[email protected]> wrote:
Send discuss mailing list submissions to [email protected]
To subscribe or unsubscribe via the World Wide Web, visit https://lists.mpich.org/mailman/listinfo/discuss or, via email, send a message with subject or body 'help' to [email protected]
You can reach the person managing the list at [email protected]
When replying, please edit your Subject line so it is more specific than "Re: Contents of discuss digest..."
Today's Topics:
1. mpich-3.2a for Blue Gene /Q omits spi libraries from the wrappers (William Scullin) 2. MPI log via MPE on CRAY XC30 machine (Milind Chabbi) 3. Passwords on small cluster (Bob Ilgner) 4. Re: Passwords on small cluster (Reuti) 5. Re: MPI log via MPE on CRAY XC30 machine (Balaji, Pavan) 6. GFORTRAN on MinGW doesn't link (Miao Li) 7. GFORTRAN on MinGW doesn't link to MPICH-2 (Miao Li) 8. Re: GFORTRAN on MinGW doesn't link (Bland, Wesley B.)
----------------------------------------------------------------------
Message: 1 Date: Tue, 16 Sep 2014 16:06:11 -0500 From: William Scullin <[email protected]> To: <[email protected]> Subject: [mpich-discuss] mpich-3.2a for Blue Gene /Q omits spi libraries from the wrappers Message-ID: <CAFmX=Zya7G_TB939v9pLnykzRUyE0O_p5p_oRn4SY0QrHz=nMA@mail.gmail.com> Content-Type: text/plain; charset="UTF-8"
When building mpich-3.2a for Blue Gene /Q and following the same procedure used for building mpich-3.1.2 for BG/Q, the required linking information for spi and pami is omitted from the wrappers. I'm not sure if this is intentional or not.
Thanks, William
Patching the wrappers to reflect the required linking gives the following diff :
[wscullin@vestasn1 ~]$ diff /projects/Operations/wscullin/mpich-3.2a1/gcc-4.4.7/bin/mpicc /projects/Operations/wscullin/mpich-3.2a1/gcc-4.4.7/bin/mpicc-postpatch 265c265 < $Show $CC $PROFILE_INCPATHS -L/bgsys/drivers/V1R2M2/ppc64/spi/lib -L/bgsys/drivers/V1R2M2/ppc64/comm/lib "${allargs[@]}" -I$includedir -L$libdir $PROFILE_PRELIB $PROFILE_FOO $rpath_flags -lmpi $PROFILE_POSTLIB ---
$Show $CC $PROFILE_INCPATHS -L/bgsys/drivers/V1R2M2/ppc64/spi/lib -L/bgsys/drivers/V1R2M2/ppc64/comm/lib "${allargs[@]}" -I$includedir -L$libdir $PROFILE_PRELIB $PROFILE_FOO $rpath_flags -lmpi $PROFILE_POSTLIB -lpami-gcc -lpthread -lSPI -lSPI_cnk -lrt -lstdc++
Full diff of mpich-3.1.2 versus 3.2a wrappers:
[wscullin@vestasn1 ~]$ diff /projects/Operations/wscullin/mpich-3.1.2/gcc-4.4.7/bin/mpicc /projects/Operations/wscullin/mpich-3.2a1/gcc-4.4.7/bin/mpicc 30,34c30,34 < prefix=/projects/Operations/wscullin/mpich-3.1.2/gcc-4.4.7 < exec_prefix=/projects/Operations/wscullin/mpich-3.1.2/gcc-4.4.7 < sysconfdir=/projects/Operations/wscullin/mpich-3.1.2/gcc-4.4.7/etc < includedir=/projects/Operations/wscullin/mpich-3.1.2/gcc-4.4.7/include < libdir=/projects/Operations/wscullin/mpich-3.1.2/gcc-4.4.7/lib ---
prefix=/projects/Operations/wscullin/mpich-3.2a1/gcc-4.4.7 exec_prefix=/projects/Operations/wscullin/mpich-3.2a1/gcc-4.4.7 sysconfdir=/projects/Operations/wscullin/mpich-3.2a1/gcc-4.4.7/etc includedir=/projects/Operations/wscullin/mpich-3.2a1/gcc-4.4.7/include libdir=/projects/Operations/wscullin/mpich-3.2a1/gcc-4.4.7/lib 40c40 < MPICH_VERSION="3.1.2"
MPICH_VERSION="3.2a1" 262c262 < $Show $CC $PROFILE_INCPATHS -L/bgsys/drivers/V1R2M2/ppc64/spi/lib -L/bgsys/drivers/V1R2M2/ppc64/comm/lib -L/bgsys/drivers/V1R2M2/ppc64/spi/lib -L/bgsys/drivers/V1R2M2/ppc64/comm/lib "${allargs[@]}" -I$includedir
$Show $CC $PROFILE_INCPATHS -L/bgsys/drivers/V1R2M2/ppc64/spi/lib -L/bgsys/drivers/V1R2M2/ppc64/comm/lib "${allargs[@]}" -I$includedir
265c265 < $Show $CC $PROFILE_INCPATHS -L/bgsys/drivers/V1R2M2/ppc64/spi/lib -L/bgsys/drivers/V1R2M2/ppc64/comm/lib -L/bgsys/drivers/V1R2M2/ppc64/spi/lib -L/bgsys/drivers/V1R2M2/ppc64/comm/lib "${allargs[@]}" -I$includedir -L$libdir $PROFILE_PRELIB $PROFILE_FOO $rpath_flags -lmpi $PROFILE_POSTLIB -lpami-gcc -lpthread -lSPI -lSPI_cnk -lrt -lstdc++ ---
$Show $CC $PROFILE_INCPATHS -L/bgsys/drivers/V1R2M2/ppc64/spi/lib -L/bgsys/drivers/V1R2M2/ppc64/comm/lib "${allargs[@]}" -I$includedir -L$libdir $PROFILE_PRELIB $PROFILE_FOO $rpath_flags -lmpi $PROFILE_POSTLIB
------------------------------
Message: 2 Date: Wed, 17 Sep 2014 00:26:05 -0500 From: Milind Chabbi <[email protected]> To: [email protected] Subject: [mpich-discuss] MPI log via MPE on CRAY XC30 machine Message-ID: <CAMmz+Y=vvO5vkwyXaKeGg1BKB+Z7zbktZJiwU3rkMjAh8Z058Q@mail.gmail.com> Content-Type: text/plain; charset=UTF-8
I am trying to gather MPI logs on CRAY XC30 (Edison machine at NERSC.) I built MPE 2-1.3 (ftp://ftp.mcs.anl.gov/pub/mpi/mpe/mpe2.tar.gz) with the following configure command:
./configure MPI_CC=cc F77=ftn MPI_F77=ftn --prefix=/XXXXX/mpe2-1.3.0-install
I compiled a simple application with the following command: /XXXX/mpe2-1.3.0-install/bin/mpecc test1.cpp -mpilog
The code compiled fine, but the execution did not generate any log files.
I am trying to generate logs files of MPI calls to view with Jumpshot on programs compiled on Cray XC30. Can you suggest the steps needed to get this working?
Thanks -Milind
------------------------------
Message: 3 Date: Wed, 17 Sep 2014 08:41:00 +0200 From: Bob Ilgner <[email protected]> To: [email protected] Subject: [mpich-discuss] Passwords on small cluster Message-ID: <CAKv15b_xROGRhPzxU3ZXka2KiC2-xz8+Vr1DHc=NYFHE-fQ6MA@mail.gmail.com> Content-Type: text/plain; charset="utf-8"
Dear all,
I am trying to run my mpi job on a small cluster with 5 nodes. When I run
mpirun -n 5 --host node01,node02,node03,node04,node05 ./hesp
the system requests a password for node01.
if I run the job only on node05 then no pasword is requested and the job runs OK Is there some way I can include a password in the host file, or otherwise ?
regards.
participants (1)
-
Miao Li