[hwloc-devel] Create success (hwloc git dev-68-gb1d497b)

[MPI Team]

Creating nightly hwloc snapshot git tarball was a success.

Snapshot:   hwloc dev-68-gb1d497b
Start time: Mon Feb  3 21:01:01 EST 2014
End time:   Mon Feb  3 21:03:24 EST 2014

Your friendly daemon,
Cyrador

[OMPI devel] 1.7.4: last call

[Ralph Castain]

Hi folks

We are about to pull the release trigger on 1.7.4, so any last-second issues 
should be surfaced immediately. Otherwise, we will release right after the OMPI 
developer's telecon on Tues morning (Pacific time).

Thanks
Ralph

Re: [OMPI devel] 1.7.4rc: additional solaris warnings

[Ralph Castain]

I fixed the two in ORTE and moved them to 1.7.4 - I suspect the others may be 
left for 1.7.5

Thanks!
Ralph

On Feb 3, 2014, at 3:22 PM, Paul Hargrove  wrote:

> The warnings below come from the Solaris Studio 12.3 compilers when testing 
> r30538 on the v1.7 branch (to confirm the undefined MB problem has been 
> resolved).
> 
> These are in addition to the shmem/{posix,svsv} ones reported yesterday.
> I am NOT saying that any/all of these are new, just that I didn't report them 
> yet.
> 
> -Paul
> 
> "[SRCDIR]/opal/mca/base/mca_base_param.c", line 583: warning: enum type 
> mismatch: op "="
> 
> "[SRCDIR]/opal/mca/hwloc/hwloc172/hwloc/src/topology-synthetic.c", line 433: 
> warning: initializer will be sign-extended: -1
> "[SRCDIR]/opal/mca/hwloc/hwloc172/hwloc/src/topology-custom.c", line 85: 
> warning: initializer will be sign-extended: -1
> "[SRCDIR]/opal/mca/hwloc/hwloc172/hwloc/src/topology-xml.c", line 1152: 
> warning: initializer will be sign-extended: -1
> 
> "[SRCDIR]/orte/mca/rmaps/base/rmaps_base_binding.c", line 975: warning: 
> statement not reached
> 
> "[SRCDIR]/orte/mca/odls/default/odls_default_module.c", line 512: warning: 
> statement not reached
> 
> "[SRCDIR]/ompi/datatype/ompi_datatype_args.c", line 515: warning: improper 
> pointer/integer combination: op "="
> 
> "[SRCDIR]/ompi/mca/io/romio/romio/adio/common/ad_fstype.c", line 315: 
> warning: statement not reached
> 
> "[SRCDIR]/ompi/mca/sharedfp/sm/sharedfp_sm_file_open.c", line 143: warning: 
> assignment type mismatch:
> pointer to struct sm_offset {struct  {..} mutex, long long offset} 
> "=" pointer to char
> "[SRCDIR]/ompi/mca/sharedfp/sm/sharedfp_sm_file_open.c", line 216: warning: 
> argument #1 is incompatible with prototype:
> prototype: pointer to char : "/usr/include/sys/mman.h", line 165
> argument : pointer to struct sm_offset {struct  {..} mutex, long long 
> offset}
> 
> 
> 
> -- 
> Paul H. Hargrove  phhargr...@lbl.gov
> Future Technologies Group
> Computer and Data Sciences Department Tel: +1-510-495-2352
> Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
> ___
> devel mailing list
> de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/devel

Re: [OMPI devel] 1.7.4rc3 static link failure on Solaris

[Paul Hargrove]

Fix confirmed.

I've confirmed that:
a) the v1.7 branch no longer fails to build due to undefined MB
b) that there is no VT issue - Nathan's patch fixed the root cause of the
problem

-Paul


On Mon, Feb 3, 2014 at 10:18 AM, Ralph Castain  wrote:

> Thanks Nathan - I fixed this in 1.7.4, and I've sent a note to the VT guys
> about the problem there. However, I won't hold things up just for the VT
> fix - we can catch it for 1.7.5
>
> Thanks Paul!
> Ralph
>
> On Feb 3, 2014, at 9:07 AM, Nathan Hjelm  wrote:
>
> > basesmuma is calling MB directly instead of calling
> > opal_atomic_[rw]mb. I fixes this in trunk and the same thing could be
> > done in 1.7 with a simple query-replace MB -> opal_atomic_wmb. ORNL was
> > using MB because opal_atomic_[rw]mb is a no-op on some platforms. I
> > don't think this should be an issue since memory access should be
> > ordered if opal_atomic_[rw]mb is a no-op. If not we should fix that in
> opal.
> >
> > -Nathan
> >
> > On Sun, Feb 02, 2014 at 01:33:41PM -0800, Paul Hargrove wrote:
> >>   Following up on my previous reports and using 1.7.4rc3:
> >>   The error I see only occurs with --enable-static.
> >>   When I do enable static libs, I get a build failure when linking
> >>   otfmerge-mpi, due to undefined symbol "MB".
> >>   When building with gcc:
> >> CCLD otfmerge-mpi
> >>   gcc: unrecognized option `-pthread'
> >>   Undefined   first referenced
> >>symbol in file
> >>   MB
> >>
>  
> /home/hargrove/OMPI/openmpi-1.7.4rc3-solaris10-sparcT2-gcc346-v9/BLD/ompi/contrib/vt/vt/../../../.libs/libmpi.so
> >>   ld: fatal: Symbol referencing errors. No output written to
> >>   .libs/otfmerge-mpi
> >>   collect2: ld returned 1 exit status
> >>   *** Error code 1
> >>   When building with Solaris Studio 12.3 compilers:
> >> CCLD otfmerge-mpi
> >>   Undefined   first referenced
> >>symbol in file
> >>   MB
> >>
>  
> /home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/BLD/ompi/contrib/vt/vt/../../../.libs/libmpi.so
> >>   ld: fatal: Symbol referencing errors. No output written to
> >>   .libs/otfmerge-mpi
> >>   *** Error code 2
> >>   This is independent of ABI (v9 vs v8plus).
> >>   If I avoid otfmerge-mpi by configuring with --disable-vt, then the
> link
> >>   failure occurs building ompi_info instead.
> >>   So, I don't think this is a vt-specific problem.  Consistent with
> that, I
> >>   found the following warnings in the make output:
> >>
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_bcast.c",
> >>   line 183: warning: implicit function declaration: MB
> >>
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_fanin.c",
> >>   line 66: warning: implicit function declaration: MB
> >>
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_fanout.c",
> >>   line 64: warning: implicit function declaration: MB
> >>
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_rk_barrier.c",
> >>   line 97: warning: implicit function declaration: MB
> >>
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_rd_nb_barrier.c",
> >>   line 75: warning: implicit function declaration: MB
> >>
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_bcast_prime.c",
> >>   line 156: warning: implicit function declaration: MB
> >>   That is all the warnings I see regarding MB (all in bcoll/basesmuma).
> >>   -Paul
> >>
> >>   On Wed, Jan 29, 2014 at 2:17 PM, Paul Hargrove 
> wrote:
> >>
> >> On Wed, Jan 29, 2014 at 9:19 AM, Paul Hargrove 
> >> wrote:
> >>
> >>   For Solaris-10 with the Solaris Studio 12.3 compilers on SPARC I
> have
> >>   encountered a link failure when configured with "--enable-static
> >>   --enable-shared" (fine w/o "--enable-static").  I have not yet
> tried
> >>   this configuration with gcc.  I have started builds of 1.7.3 to
> >>   determine if this is a regression or not before investing more
> deeply.
> >>I hope to be able to report more tonight.
> >>
> >> The problem is also present in 1.7.3 and thus NOT a (recent)
> regression.
> >> More information will follow eventually, but knowing that this
> problem
> >> isn't new significantly reduces the urgency (at least for me).
> >> -Paul
> >> --
> >> Paul H. Hargrove  phhargr...@lbl.gov
> >> Future Technologies Group
> >> Computer and Data Sciences Department Tel: +1-510-495-2352
> >> Lawrence 

[OMPI devel] 1.7.4rc: additional solaris warnings

[Paul Hargrove]

The warnings below come from the Solaris Studio 12.3 compilers when testing
r30538 on the v1.7 branch (to confirm the undefined MB problem has been
resolved).

These are in addition to the shmem/{posix,svsv} ones reported yesterday.
I am NOT saying that any/all of these are new, just that I didn't report
them yet.

-Paul

"[SRCDIR]/opal/mca/base/mca_base_param.c", line 583: warning: enum type
mismatch: op "="

"[SRCDIR]/opal/mca/hwloc/hwloc172/hwloc/src/topology-synthetic.c", line
433: warning: initializer will be sign-extended: -1
"[SRCDIR]/opal/mca/hwloc/hwloc172/hwloc/src/topology-custom.c", line 85:
warning: initializer will be sign-extended: -1
"[SRCDIR]/opal/mca/hwloc/hwloc172/hwloc/src/topology-xml.c", line 1152:
warning: initializer will be sign-extended: -1

"[SRCDIR]/orte/mca/rmaps/base/rmaps_base_binding.c", line 975: warning:
statement not reached

"[SRCDIR]/orte/mca/odls/default/odls_default_module.c", line 512: warning:
statement not reached

"[SRCDIR]/ompi/datatype/ompi_datatype_args.c", line 515: warning: improper
pointer/integer combination: op "="

"[SRCDIR]/ompi/mca/io/romio/romio/adio/common/ad_fstype.c", line 315:
warning: statement not reached

"[SRCDIR]/ompi/mca/sharedfp/sm/sharedfp_sm_file_open.c", line 143: warning:
assignment type mismatch:
pointer to struct sm_offset {struct  {..} mutex, long long offset}
"=" pointer to char
"[SRCDIR]/ompi/mca/sharedfp/sm/sharedfp_sm_file_open.c", line 216: warning:
argument #1 is incompatible with prototype:
prototype: pointer to char : "/usr/include/sys/mman.h", line 165
argument : pointer to struct sm_offset {struct  {..} mutex, long
long offset}



-- 
Paul H. Hargrove  phhargr...@lbl.gov
Future Technologies Group
Computer and Data Sciences Department Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory Fax: +1-510-486-6900

Re: [OMPI devel] Problem compiling openmpi 1.7.4rc3 against system libevent

[Ralph Castain]

Thanks! I'll add your patch.


On Feb 3, 2014, at 12:49 PM, Orion Poplawski  wrote:

> When I try to compile openmpi 1.7.4rc3 against a system libevent I get
> an error about OPAL_LIKELY being undefined in opal-hotel.o.  This patch
> fixes.
> 
> -- 
> Orion Poplawski
> Technical Manager 303-415-9701 x222
> NWRA/CoRA DivisionFAX: 303-415-9702
> 3380 Mitchell Lane  or...@cora.nwra.com
> Boulder, CO 80301  http://www.cora.nwra.com
> ___
> devel mailing list
> de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/devel

[OMPI devel] Problem compiling openmpi 1.7.4rc3 against system libevent

[Orion Poplawski]

When I try to compile openmpi 1.7.4rc3 against a system libevent I get
an error about OPAL_LIKELY being undefined in opal-hotel.o.  This patch
fixes.

-- 
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA DivisionFAX: 303-415-9702
3380 Mitchell Lane  or...@cora.nwra.com
Boulder, CO 80301  http://www.cora.nwra.com
diff -up openmpi-1.7.4rc3/opal/class/opal_hotel.h.includes openmpi-1.7.4rc3/opal/class/opal_hotel.h
--- openmpi-1.7.4rc3/opal/class/opal_hotel.h.includes	2013-09-26 12:22:54.0 -0600
+++ openmpi-1.7.4rc3/opal/class/opal_hotel.h	2014-02-03 13:09:22.542594690 -0700
@@ -54,6 +54,7 @@

 #include "opal/class/opal_object.h"
 #include "opal/mca/event/event.h"
+#include "opal/prefetch.h"

 BEGIN_C_DECLS

Re: [OMPI devel] Use unique collective ids for the checkpoint/restart code

[Ralph Castain]

Looks okay to me - I see you left a "printf" statement in 
plm_base_launch_support.c, so you might want to make that an 
opal_output_verbose or something.

On Feb 3, 2014, at 12:19 PM, Adrian Reber  wrote:

> This patch
> 
> https://lisas.de/git/?p=open-mpi.git;a=commitdiff;h=14ec7f42baab882e345948ff79c4f75f5084bbbf
> 
> introduces unique collective ids for the checkpoint/restart code and
> with this applied it seems to work pretty good. As this patch also
> touches non-CR code it would be good if someone could have a look at it.
> 
> With this patch applied the code seems to work up to the point where
> orterun actually pauses all processes and tries to create the
> checkpoints. The checkpoint creation does not work for me as CRS does
> not yet include support for checkpoint/restart using CRIU which would be
> my next step.
> 
>   Adrian
> ___
> devel mailing list
> de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/devel

[OMPI devel] Use unique collective ids for the checkpoint/restart code

[Adrian Reber]

This patch

https://lisas.de/git/?p=open-mpi.git;a=commitdiff;h=14ec7f42baab882e345948ff79c4f75f5084bbbf

introduces unique collective ids for the checkpoint/restart code and
with this applied it seems to work pretty good. As this patch also
touches non-CR code it would be good if someone could have a look at it.

With this patch applied the code seems to work up to the point where
orterun actually pauses all processes and tries to create the
checkpoints. The checkpoint creation does not work for me as CRS does
not yet include support for checkpoint/restart using CRIU which would be
my next step.

Adrian

Re: [OMPI devel] 1.7.4rc3: solaris warnings in shmem/posix and shmem/sysv

[Ralph Castain]

Committed a fix for these in the trunk - I've asked Jeff to review for 1.7.4, 
but let me know if you get a chance to verify it

Thanks!
Ralph

On Feb 2, 2014, at 1:46 PM, Paul Hargrove  wrote:

> I see the following warnings when building 1.7.4rc3 on Solaris10 on SPARC w/ 
> the Solaris Studio 12.3 compilers.
> 
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/opal/mca/shmem/posix/shmem_posix_common_utils.c",
>  line 75: warning: implicit function declaration: shm_open
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/opal/mca/shmem/posix/shmem_
> posix_component.c", line 186: warning: implicit function declaration: 
> shm_unlink
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/opal/mca/shmem/posix/shmem_posix_module.c",
>  line 212: warning: assignment type mismatch:
> pointer to struct opal_shmem_seg_hdr_t {struct opal_atomic_lock_t 
> {..} lock, int cpid} "=" pointer to char
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/opal/mca/shmem/posix/shmem_posix_module.c",
>  line 285: warning: implicit function declaration: shm_unlink
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/opal/mca/shmem/posix/shmem_posix_module.c",
>  line 288: warning: argument #1 is incompatible with prototype:
> prototype: pointer to char : "/usr/include/sys/mman.h", line 165
> argument : pointer to struct opal_shmem_seg_hdr_t {struct 
> opal_atomic_lock_t {..} lock, int cpid}
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/opal/mca/shmem/posix/shmem_posix_module.c",
>  line 306: warning: implicit function declaration: shm_open
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/opal/mca/shmem/posix/shmem_posix_module.c",
>  line 315: warning: assignment type mismatch:
> pointer to unsigned char "=" pointer to char
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/opal/mca/shmem/posix/shmem_posix_module.c",
>  line 378: warning: argument #1 is incompatible with prototype:
> prototype: pointer to char : "/usr/include/sys/mman.h", line 165
> argument : pointer to unsigned char
>   
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/opal/mca/shmem/sysv/shmem_sysv_module.c",
>  line 278: warning: argument #1 is incompatible with prototype:
> prototype: pointer to char : "/usr/include/sys/shm.h", line 131
> argument : pointer to struct opal_shmem_seg_hdr_t {struct 
> opal_atomic_lock_t {..} lock, int cpid}
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/opal/mca/shmem/sysv/shmem_sysv_module.c",
>  line 342: warning: argument #1 is incompatible with prototype:
> prototype: pointer to char : "/usr/include/sys/shm.h", line 131
> argument : pointer to unsigned char
> 
> Some appear to be missing casts for pointer types (as args and in 
> assignments).
> 
> Others seem to be missing prototypes for shm_*(), despite including the right 
> headers.
> In GASNet we found we need to deal with POSIX shared memory as follows on 
> Solaris:
> 
> #if PLATFORM_OS_SOLARIS && !defined(_POSIX_C_SOURCE)
>   #define _POSIX_C_SOURCE 200112L /* Required for shm_{open,unlink} decls */
>   #include 
>   #undef _POSIX_C_SOURCE
> #elif HAVE_SYS_MMAN_H
>   #include 
> #else
>   
> #endif
> 
> -Paul
> 
> -- 
> Paul H. Hargrove  phhargr...@lbl.gov
> Future Technologies Group
> Computer and Data Sciences Department Tel: +1-510-495-2352
> Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
> ___
> devel mailing list
> de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/devel

Re: [OMPI devel] Speedup for MPI_Dims_create()

[Jeff Squyres (jsquyres)]

Andreas --

I added the sqrt() change, which is the most important change, and then did a 
2nd commit with the whitespace cleanup.  The sqrt change will likely be in 
1.7.5.  I credited you in the commit log; you'll likely also get credited in 
NEWS.

Thank you for the patch!


On Dec 19, 2013, at 9:37 AM, Andreas Schäfer  wrote:

> Dear all,
> 
> please find attached a (trivial) patch to MPI_Dims_create(). When
> computing the prime factors of nnodes, it is sufficient to check for
> primes less or equal to sqrt(nnodes).
> 
> This was not so much of a problem in the past, but now that Tier 0
> systems are capable of running O(10^6) MPI processes, the difference
> in execution time is on the order of seconds (e.g. 8.86s vs. 0.04s on
> my notebook, with nnproc = 10^6).
> 
> Best
> -Andreas
> 
> PS: oh, and the patch removes some trailing whitespace. Yuck. :-)
> 
> 
> -- 
> ==
> Andreas Schäfer
> HPC and Grid Computing
> Chair of Computer Science 3
> Friedrich-Alexander-Universität Erlangen-Nürnberg, Germany
> +49 9131 85-27910
> PGP/GPG key via keyserver
> http://www.libgeodecomp.org
> ==
> 
> (\___/)
> (+'.'+)
> (")_(")
> This is Bunny. Copy and paste Bunny into your
> signature to help him gain world domination!
> ___
> devel mailing list
> de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/devel


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

Re: [OMPI devel] 1.7.4rc3 static link failure on Solaris

[Bert Wesarg]

Ralph,

On 02/03/2014 07:18 PM, Ralph Castain wrote:

Thanks Nathan - I fixed this in 1.7.4, and I've sent a note to the VT guys 
about the problem there. However, I won't hold things up just for the VT fix - 
we can catch it for 1.7.5


most of OUR VT team is currently not available, and I didn't get the 
message form you yet. But what exactly is the problem with VT in this 
report? Paul already noted that a build with --disable-vt has the same 
link error in ompi_info.


Bert



Thanks Paul!
Ralph

On Feb 3, 2014, at 9:07 AM, Nathan Hjelm  wrote:


basesmuma is calling MB directly instead of calling
opal_atomic_[rw]mb. I fixes this in trunk and the same thing could be
done in 1.7 with a simple query-replace MB -> opal_atomic_wmb. ORNL was
using MB because opal_atomic_[rw]mb is a no-op on some platforms. I
don't think this should be an issue since memory access should be
ordered if opal_atomic_[rw]mb is a no-op. If not we should fix that in opal.

-Nathan

On Sun, Feb 02, 2014 at 01:33:41PM -0800, Paul Hargrove wrote:

   Following up on my previous reports and using 1.7.4rc3:
   The error I see only occurs with --enable-static.
   When I do enable static libs, I get a build failure when linking
   otfmerge-mpi, due to undefined symbol "MB".
   When building with gcc:
 CCLD otfmerge-mpi
   gcc: unrecognized option `-pthread'
   Undefined   first referenced
symbol in file
   MB

/home/hargrove/OMPI/openmpi-1.7.4rc3-solaris10-sparcT2-gcc346-v9/BLD/ompi/contrib/vt/vt/../../../.libs/libmpi.so
   ld: fatal: Symbol referencing errors. No output written to
   .libs/otfmerge-mpi
   collect2: ld returned 1 exit status
   *** Error code 1
   When building with Solaris Studio 12.3 compilers:
 CCLD otfmerge-mpi
   Undefined   first referenced
symbol in file
   MB

/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/BLD/ompi/contrib/vt/vt/../../../.libs/libmpi.so
   ld: fatal: Symbol referencing errors. No output written to
   .libs/otfmerge-mpi
   *** Error code 2
   This is independent of ABI (v9 vs v8plus).
   If I avoid otfmerge-mpi by configuring with --disable-vt, then the link
   failure occurs building ompi_info instead.
   So, I don't think this is a vt-specific problem.  Consistent with that, I
   found the following warnings in the make output:
   
"/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_bcast.c",
   line 183: warning: implicit function declaration: MB
   
"/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_fanin.c",
   line 66: warning: implicit function declaration: MB
   
"/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_fanout.c",
   line 64: warning: implicit function declaration: MB
   
"/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_rk_barrier.c",
   line 97: warning: implicit function declaration: MB
   
"/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_rd_nb_barrier.c",
   line 75: warning: implicit function declaration: MB
   
"/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_bcast_prime.c",
   line 156: warning: implicit function declaration: MB
   That is all the warnings I see regarding MB (all in bcoll/basesmuma).
   -Paul

   On Wed, Jan 29, 2014 at 2:17 PM, Paul Hargrove  wrote:

 On Wed, Jan 29, 2014 at 9:19 AM, Paul Hargrove 
 wrote:

   For Solaris-10 with the Solaris Studio 12.3 compilers on SPARC I have
   encountered a link failure when configured with "--enable-static
   --enable-shared" (fine w/o "--enable-static").  I have not yet tried
   this configuration with gcc.  I have started builds of 1.7.3 to
   determine if this is a regression or not before investing more deeply.
I hope to be able to report more tonight.

 The problem is also present in 1.7.3 and thus NOT a (recent) regression.
 More information will follow eventually, but knowing that this problem
 isn't new significantly reduces the urgency (at least for me).
 -Paul
 --
 Paul H. Hargrove  phhargr...@lbl.gov
 Future Technologies Group
 Computer and Data Sciences Department Tel: +1-510-495-2352
 Lawrence Berkeley National Laboratory Fax: +1-510-486-6900

   --
   Paul H. Hargrove  phhargr...@lbl.gov
   Future Technologies Group
   Computer and Data Sciences Department Tel: +1-510-495-2352
   Lawrence Berkeley National Laboratory Fax: +1-510-486-6900

Re: [OMPI devel] 1.7.4rc3 static link failure on Solaris

[Paul Hargrove]

Ralph,

Not sure there ever *was* a VT problem.
I think the issue is just showed up there as the first "CCLD" which linked
libmpi.a
Since this is a static build, the "bare" MB calls in the bcol/basesmuma
caused problems.
I will try to confirm ASAP

Rather than wait for the nightly tarball I am going to try
(svn+autogen)+rsync.  Wish me luck :-).

-Paul


On Mon, Feb 3, 2014 at 10:18 AM, Ralph Castain  wrote:

> Thanks Nathan - I fixed this in 1.7.4, and I've sent a note to the VT guys
> about the problem there. However, I won't hold things up just for the VT
> fix - we can catch it for 1.7.5
>
> Thanks Paul!
> Ralph
>
> On Feb 3, 2014, at 9:07 AM, Nathan Hjelm  wrote:
>
> > basesmuma is calling MB directly instead of calling
> > opal_atomic_[rw]mb. I fixes this in trunk and the same thing could be
> > done in 1.7 with a simple query-replace MB -> opal_atomic_wmb. ORNL was
> > using MB because opal_atomic_[rw]mb is a no-op on some platforms. I
> > don't think this should be an issue since memory access should be
> > ordered if opal_atomic_[rw]mb is a no-op. If not we should fix that in
> opal.
> >
> > -Nathan
> >
> > On Sun, Feb 02, 2014 at 01:33:41PM -0800, Paul Hargrove wrote:
> >>   Following up on my previous reports and using 1.7.4rc3:
> >>   The error I see only occurs with --enable-static.
> >>   When I do enable static libs, I get a build failure when linking
> >>   otfmerge-mpi, due to undefined symbol "MB".
> >>   When building with gcc:
> >> CCLD otfmerge-mpi
> >>   gcc: unrecognized option `-pthread'
> >>   Undefined   first referenced
> >>symbol in file
> >>   MB
> >>
>  
> /home/hargrove/OMPI/openmpi-1.7.4rc3-solaris10-sparcT2-gcc346-v9/BLD/ompi/contrib/vt/vt/../../../.libs/libmpi.so
> >>   ld: fatal: Symbol referencing errors. No output written to
> >>   .libs/otfmerge-mpi
> >>   collect2: ld returned 1 exit status
> >>   *** Error code 1
> >>   When building with Solaris Studio 12.3 compilers:
> >> CCLD otfmerge-mpi
> >>   Undefined   first referenced
> >>symbol in file
> >>   MB
> >>
>  
> /home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/BLD/ompi/contrib/vt/vt/../../../.libs/libmpi.so
> >>   ld: fatal: Symbol referencing errors. No output written to
> >>   .libs/otfmerge-mpi
> >>   *** Error code 2
> >>   This is independent of ABI (v9 vs v8plus).
> >>   If I avoid otfmerge-mpi by configuring with --disable-vt, then the
> link
> >>   failure occurs building ompi_info instead.
> >>   So, I don't think this is a vt-specific problem.  Consistent with
> that, I
> >>   found the following warnings in the make output:
> >>
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_bcast.c",
> >>   line 183: warning: implicit function declaration: MB
> >>
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_fanin.c",
> >>   line 66: warning: implicit function declaration: MB
> >>
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_fanout.c",
> >>   line 64: warning: implicit function declaration: MB
> >>
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_rk_barrier.c",
> >>   line 97: warning: implicit function declaration: MB
> >>
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_rd_nb_barrier.c",
> >>   line 75: warning: implicit function declaration: MB
> >>
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_bcast_prime.c",
> >>   line 156: warning: implicit function declaration: MB
> >>   That is all the warnings I see regarding MB (all in bcoll/basesmuma).
> >>   -Paul
> >>
> >>   On Wed, Jan 29, 2014 at 2:17 PM, Paul Hargrove 
> wrote:
> >>
> >> On Wed, Jan 29, 2014 at 9:19 AM, Paul Hargrove 
> >> wrote:
> >>
> >>   For Solaris-10 with the Solaris Studio 12.3 compilers on SPARC I
> have
> >>   encountered a link failure when configured with "--enable-static
> >>   --enable-shared" (fine w/o "--enable-static").  I have not yet
> tried
> >>   this configuration with gcc.  I have started builds of 1.7.3 to
> >>   determine if this is a regression or not before investing more
> deeply.
> >>I hope to be able to report more tonight.
> >>
> >> The problem is also present in 1.7.3 and thus NOT a (recent)
> regression.
> >> More information will follow eventually, but knowing that this
> problem
> >> isn't new significantly reduces the urgency (at least for me).
> >> -Paul
> >> --
> >> Paul H. Hargrove

Re: [OMPI devel] 1.7.4rc3 static link failure on Solaris

[Ralph Castain]

Thanks Nathan - I fixed this in 1.7.4, and I've sent a note to the VT guys 
about the problem there. However, I won't hold things up just for the VT fix - 
we can catch it for 1.7.5

Thanks Paul!
Ralph

On Feb 3, 2014, at 9:07 AM, Nathan Hjelm  wrote:

> basesmuma is calling MB directly instead of calling
> opal_atomic_[rw]mb. I fixes this in trunk and the same thing could be
> done in 1.7 with a simple query-replace MB -> opal_atomic_wmb. ORNL was
> using MB because opal_atomic_[rw]mb is a no-op on some platforms. I
> don't think this should be an issue since memory access should be
> ordered if opal_atomic_[rw]mb is a no-op. If not we should fix that in opal.
> 
> -Nathan
> 
> On Sun, Feb 02, 2014 at 01:33:41PM -0800, Paul Hargrove wrote:
>>   Following up on my previous reports and using 1.7.4rc3:
>>   The error I see only occurs with --enable-static.
>>   When I do enable static libs, I get a build failure when linking
>>   otfmerge-mpi, due to undefined symbol "MB".
>>   When building with gcc:
>> CCLD otfmerge-mpi
>>   gcc: unrecognized option `-pthread'
>>   Undefined   first referenced
>>symbol in file
>>   MB
>>
>> /home/hargrove/OMPI/openmpi-1.7.4rc3-solaris10-sparcT2-gcc346-v9/BLD/ompi/contrib/vt/vt/../../../.libs/libmpi.so
>>   ld: fatal: Symbol referencing errors. No output written to
>>   .libs/otfmerge-mpi
>>   collect2: ld returned 1 exit status
>>   *** Error code 1
>>   When building with Solaris Studio 12.3 compilers:
>> CCLD otfmerge-mpi
>>   Undefined   first referenced
>>symbol in file
>>   MB
>>
>> /home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/BLD/ompi/contrib/vt/vt/../../../.libs/libmpi.so
>>   ld: fatal: Symbol referencing errors. No output written to
>>   .libs/otfmerge-mpi
>>   *** Error code 2
>>   This is independent of ABI (v9 vs v8plus).
>>   If I avoid otfmerge-mpi by configuring with --disable-vt, then the link
>>   failure occurs building ompi_info instead.
>>   So, I don't think this is a vt-specific problem.  Consistent with that, I
>>   found the following warnings in the make output:
>>   
>> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_bcast.c",
>>   line 183: warning: implicit function declaration: MB
>>   
>> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_fanin.c",
>>   line 66: warning: implicit function declaration: MB
>>   
>> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_fanout.c",
>>   line 64: warning: implicit function declaration: MB
>>   
>> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_rk_barrier.c",
>>   line 97: warning: implicit function declaration: MB
>>   
>> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_rd_nb_barrier.c",
>>   line 75: warning: implicit function declaration: MB
>>   
>> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_bcast_prime.c",
>>   line 156: warning: implicit function declaration: MB
>>   That is all the warnings I see regarding MB (all in bcoll/basesmuma).
>>   -Paul
>> 
>>   On Wed, Jan 29, 2014 at 2:17 PM, Paul Hargrove  wrote:
>> 
>> On Wed, Jan 29, 2014 at 9:19 AM, Paul Hargrove 
>> wrote:
>> 
>>   For Solaris-10 with the Solaris Studio 12.3 compilers on SPARC I have
>>   encountered a link failure when configured with "--enable-static
>>   --enable-shared" (fine w/o "--enable-static").  I have not yet tried
>>   this configuration with gcc.  I have started builds of 1.7.3 to
>>   determine if this is a regression or not before investing more deeply.
>>I hope to be able to report more tonight.
>> 
>> The problem is also present in 1.7.3 and thus NOT a (recent) regression.
>> More information will follow eventually, but knowing that this problem
>> isn't new significantly reduces the urgency (at least for me).
>> -Paul
>> --
>> Paul H. Hargrove  phhargr...@lbl.gov
>> Future Technologies Group
>> Computer and Data Sciences Department Tel: +1-510-495-2352
>> Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
>> 
>>   --
>>   Paul H. Hargrove  phhargr...@lbl.gov
>>   Future Technologies Group
>>   Computer and Data Sciences Department Tel: +1-510-495-2352
>>   Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
> 
>> ___
>> 

Re: [OMPI devel] 1.7.4rc3 static link failure on Solaris

[Nathan Hjelm]

basesmuma is calling MB directly instead of calling
opal_atomic_[rw]mb. I fixes this in trunk and the same thing could be
done in 1.7 with a simple query-replace MB -> opal_atomic_wmb. ORNL was
using MB because opal_atomic_[rw]mb is a no-op on some platforms. I
don't think this should be an issue since memory access should be
ordered if opal_atomic_[rw]mb is a no-op. If not we should fix that in opal.

-Nathan

On Sun, Feb 02, 2014 at 01:33:41PM -0800, Paul Hargrove wrote:
>Following up on my previous reports and using 1.7.4rc3:
>The error I see only occurs with --enable-static.
>When I do enable static libs, I get a build failure when linking
>otfmerge-mpi, due to undefined symbol "MB".
>When building with gcc:
>  CCLD otfmerge-mpi
>gcc: unrecognized option `-pthread'
>Undefined   first referenced
> symbol in file
>MB
> 
> /home/hargrove/OMPI/openmpi-1.7.4rc3-solaris10-sparcT2-gcc346-v9/BLD/ompi/contrib/vt/vt/../../../.libs/libmpi.so
>ld: fatal: Symbol referencing errors. No output written to
>.libs/otfmerge-mpi
>collect2: ld returned 1 exit status
>*** Error code 1
>When building with Solaris Studio 12.3 compilers:
>  CCLD otfmerge-mpi
>Undefined   first referenced
> symbol in file
>MB
> 
> /home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/BLD/ompi/contrib/vt/vt/../../../.libs/libmpi.so
>ld: fatal: Symbol referencing errors. No output written to
>.libs/otfmerge-mpi
>*** Error code 2
>This is independent of ABI (v9 vs v8plus).
>If I avoid otfmerge-mpi by configuring with --disable-vt, then the link
>failure occurs building ompi_info instead.
>So, I don't think this is a vt-specific problem.  Consistent with that, I
>found the following warnings in the make output:
>
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_bcast.c",
>line 183: warning: implicit function declaration: MB
>
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_fanin.c",
>line 66: warning: implicit function declaration: MB
>
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_fanout.c",
>line 64: warning: implicit function declaration: MB
>
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_rk_barrier.c",
>line 97: warning: implicit function declaration: MB
>
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_rd_nb_barrier.c",
>line 75: warning: implicit function declaration: MB
>
> "/home/hargrove/OMPI/openmpi-1.7.4rc2-solaris10-sparcT2-ss12u3-v9/openmpi-1.7.4rc2/ompi/mca/bcol/basesmuma/bcol_basesmuma_bcast_prime.c",
>line 156: warning: implicit function declaration: MB
>That is all the warnings I see regarding MB (all in bcoll/basesmuma).
>-Paul
> 
>On Wed, Jan 29, 2014 at 2:17 PM, Paul Hargrove  wrote:
> 
>  On Wed, Jan 29, 2014 at 9:19 AM, Paul Hargrove 
>  wrote:
> 
>For Solaris-10 with the Solaris Studio 12.3 compilers on SPARC I have
>encountered a link failure when configured with "--enable-static
>--enable-shared" (fine w/o "--enable-static").  I have not yet tried
>this configuration with gcc.  I have started builds of 1.7.3 to
>determine if this is a regression or not before investing more deeply.
> I hope to be able to report more tonight.
> 
>  The problem is also present in 1.7.3 and thus NOT a (recent) regression.
>  More information will follow eventually, but knowing that this problem
>  isn't new significantly reduces the urgency (at least for me).
>  -Paul
>  --
>  Paul H. Hargrove  phhargr...@lbl.gov
>  Future Technologies Group
>  Computer and Data Sciences Department Tel: +1-510-495-2352
>  Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
> 
>--
>Paul H. Hargrove  phhargr...@lbl.gov
>Future Technologies Group
>Computer and Data Sciences Department Tel: +1-510-495-2352
>Lawrence Berkeley National Laboratory Fax: +1-510-486-6900

> ___
> devel mailing list
> de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/devel



pgpvFPI3ME5Ft.pgp
Description: PGP signature

Re: [OMPI devel] OMPI 1.7 compilation error with icc

[Jeff Squyres (jsquyres)]

Ah -- make dist when using icc/ifort was the magic combination that fails (it 
wouldn't fail when using gcc/gfortran).

Ok, I see the problem -- fix coming shortly.  Thanks for finding it!


On Feb 3, 2014, at 7:44 AM, Mike Dubman  wrote:

> more info:
> 
> to reproduce, "./autogen.sh && ./configure && make dist" on rhel 6.4
> 
> 
> On Mon, Feb 3, 2014 at 12:39 PM, Mike Dubman  wrote:
> (cd scripts && make  top_distdir=../../../../../openmpi-1.7.4rc4git 
> distdir=../../../../../openmpi-1.7.4rc4git/ompi/mpi/fortran/use-mpi-tkr/scripts
>  \
>  am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir)
> make[4]: Entering directory 
> `/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-tkr/scripts'
> make[4]: Leaving directory 
> `/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-tkr/scripts'
> make[3]: Leaving directory 
> `/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-tkr'
>  (cd mpi/fortran/use-mpi-ignore-tkr && make  
> top_distdir=../../../../openmpi-1.7.4rc4git 
> distdir=../../../../openmpi-1.7.4rc4git/ompi/mpi/fortran/use-mpi-ignore-tkr \
>  am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir)
> make[3]: Entering directory 
> `/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-ignore-tkr'
> make[3]: Leaving directory 
> `/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-ignore-tkr'
>  (cd mpi/fortran/use-mpi-f08 && make  
> top_distdir=../../../../openmpi-1.7.4rc4git 
> distdir=../../../../openmpi-1.7.4rc4git/ompi/mpi/fortran/use-mpi-f08 \
>  am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir)
> make[3]: Entering directory 
> `/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-f08'
> make[3]: Leaving directory 
> `/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-f08'
>  (cd mpi/fortran/use-mpi-f08-desc && make  
> top_distdir=../../../../openmpi-1.7.4rc4git 
> distdir=../../../../openmpi-1.7.4rc4git/ompi/mpi/fortran/use-mpi-f08-desc \
>  am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir)
> make[3]: Entering directory 
> `/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-f08-desc'
>   FC   mpi-f08-types.lo
> mpi-f08-types.f90(83): error #6418: This name has already been assigned a 
> data type.   [MPI_SUBARRAYS_SUPPORTED]
>   logical, parameter :: MPI_SUBARRAYS_SUPPORTED = .true.
> ^
> compilation aborted for mpi-f08-types.f90 (code 1)
> make[3]: *** [mpi-f08-types.lo] Error 1
> make[3]: Leaving directory 
> `/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-f08-desc'
> make[2]: *** [distdir] Error 1
> make[2]: Leaving directory 
> `/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi'
> make[1]: *** [distdir] Error 1
> make[1]: Leaving directory 
> `/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7'
> make: *** [dist] Error 2
> 
> 
> ___
> devel mailing list
> de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/devel


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

Re: [OMPI devel] OMPI 1.7 compilation error with icc

[Mike Dubman]

more info:

to reproduce, "./autogen.sh && ./configure && make dist" on rhel 6.4


On Mon, Feb 3, 2014 at 12:39 PM, Mike Dubman wrote:

> (cd scripts && make  top_distdir=../../../../../openmpi-1.7.4rc4git
> distdir=../../../../../openmpi-1.7.4rc4git/ompi/mpi/fortran/use-mpi-tkr/scripts
> \
>  am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=:
> distdir)
> make[4]: Entering directory
> `/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-tkr/scripts'
> make[4]: Leaving directory
> `/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-tkr/scripts'
> make[3]: Leaving directory
> `/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-tkr'
>  (cd mpi/fortran/use-mpi-ignore-tkr && make
>  top_distdir=../../../../openmpi-1.7.4rc4git
> distdir=../../../../openmpi-1.7.4rc4git/ompi/mpi/fortran/use-mpi-ignore-tkr
> \
>  am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=:
> distdir)
> make[3]: Entering directory
> `/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-ignore-tkr'
> make[3]: Leaving directory
> `/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-ignore-tkr'
>  (cd mpi/fortran/use-mpi-f08 && make
>  top_distdir=../../../../openmpi-1.7.4rc4git
> distdir=../../../../openmpi-1.7.4rc4git/ompi/mpi/fortran/use-mpi-f08 \
>  am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=:
> distdir)
> make[3]: Entering directory
> `/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-f08'
> make[3]: Leaving directory
> `/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-f08'
>  (cd mpi/fortran/use-mpi-f08-desc && make
>  top_distdir=../../../../openmpi-1.7.4rc4git
> distdir=../../../../openmpi-1.7.4rc4git/ompi/mpi/fortran/use-mpi-f08-desc \
>  am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=:
> distdir)
> make[3]: Entering directory
> `/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-f08-desc'
>   FC   mpi-f08-types.lo
> mpi-f08-types.f90(83): error #6418: This name has already been assigned a
> data type.   [MPI_SUBARRAYS_SUPPORTED]
>   logical, parameter :: MPI_SUBARRAYS_SUPPORTED = .true.
> ^
> compilation aborted for mpi-f08-types.f90 (code 1)
> make[3]: *** [mpi-f08-types.lo] Error 1
> make[3]: Leaving directory
> `/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-f08-desc'
> make[2]: *** [distdir] Error 1
> make[2]: Leaving directory
> `/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi'
> make[1]: *** [distdir] Error 1
> make[1]: Leaving directory
> `/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7'
> make: *** [dist] Error 2
>
>

[OMPI devel] OMPI 1.7 compilation error with icc

[Mike Dubman]

(cd scripts && make  top_distdir=../../../../../openmpi-1.7.4rc4git
distdir=../../../../../openmpi-1.7.4rc4git/ompi/mpi/fortran/use-mpi-tkr/scripts
\
 am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=:
distdir)
make[4]: Entering directory
`/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-tkr/scripts'
make[4]: Leaving directory
`/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-tkr/scripts'
make[3]: Leaving directory
`/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-tkr'
 (cd mpi/fortran/use-mpi-ignore-tkr && make
 top_distdir=../../../../openmpi-1.7.4rc4git
distdir=../../../../openmpi-1.7.4rc4git/ompi/mpi/fortran/use-mpi-ignore-tkr
\
 am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=:
distdir)
make[3]: Entering directory
`/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-ignore-tkr'
make[3]: Leaving directory
`/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-ignore-tkr'
 (cd mpi/fortran/use-mpi-f08 && make
 top_distdir=../../../../openmpi-1.7.4rc4git
distdir=../../../../openmpi-1.7.4rc4git/ompi/mpi/fortran/use-mpi-f08 \
 am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=:
distdir)
make[3]: Entering directory
`/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-f08'
make[3]: Leaving directory
`/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-f08'
 (cd mpi/fortran/use-mpi-f08-desc && make
 top_distdir=../../../../openmpi-1.7.4rc4git
distdir=../../../../openmpi-1.7.4rc4git/ompi/mpi/fortran/use-mpi-f08-desc \
 am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=:
distdir)
make[3]: Entering directory
`/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-f08-desc'
  FC   mpi-f08-types.lo
mpi-f08-types.f90(83): error #6418: This name has already been assigned a
data type.   [MPI_SUBARRAYS_SUPPORTED]
  logical, parameter :: MPI_SUBARRAYS_SUPPORTED = .true.
^
compilation aborted for mpi-f08-types.f90 (code 1)
make[3]: *** [mpi-f08-types.lo] Error 1
make[3]: Leaving directory
`/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi/mpi/fortran/use-mpi-f08-desc'
make[2]: *** [distdir] Error 1
make[2]: Leaving directory
`/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7/ompi'
make[1]: *** [distdir] Error 1
make[1]: Leaving directory
`/hpc/local/benchmarks/hpc-stack-icc/src/install/ompi-v1.7'
make: *** [dist] Error 2