Re: [OMPI devel] Was "hcoll destruction via MPI attribute": undefined symbol hcoll_group_destroy_notify

2014-04-08 Thread Joshua Ladd
In order to run with OMPI 1.8, we need to get you the latest HCOLL drop. Mike Dubman can handle this for you. He will be back in the office Thursday sometime. Best, Josh From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Anthony Alba Sent: Tuesday, April 08, 2014 9:59 PM To: de...@ope

[OMPI devel] Was "hcoll destruction via MPI attribute": undefined symbol hcoll_group_destroy_notify

2014-04-08 Thread Anthony Alba
Running OMPI 1.8 with Mellanox OFED 2.1-1.0.6, with --with-hcoll=/opt/mellanox/hcoll The symbol hcoll_group_destroy_notify() is used in ompi/mca/coll/hcoll/coll_hcoll_module.c but I cannot find it exported anywhere. It is not in /opt/mellanox/hcoll/lib/lib*so nm /opt/mellanox/hcoll/lib/lib*so

Re: [OMPI devel] Problem of running 'mpirun' on a cross-compiled openmpi-1.6.5 for armv7

2014-04-08 Thread Allan Wu
Thank you, Ralph and Jeff! After I downloaded the new version (1.8) and recompiled it based on your suggestions, it finally works for me, at least for a few helloworld-like applications. For future references, here is the configuration script I used: ./configure --build=arm-linux-gnueabi --host=a

[OMPI devel] OMPI www repo now at github

2014-04-08 Thread Jeff Squyres (jsquyres)
Effective immediately, the Open MPI web site repository (i.e., all the PHP that runs www.open-mpi.org) is now at github (it used to be in svn.open-mpi.org): https://github.com/open-mpi/ompi-www Read access to the old SVN repo is still available, but write access has been disabled. The old

[OMPI devel] RFC: more ob1 optimizations

2014-04-08 Thread Nathan Hjelm
What: Add an optimization for isend in pml/ob1. This optimization is a companion to the optimizations recently committed to 1.8.1. The basic idea is if the btl supports inline sends and the message is small (currently hardcoded but planned to be configurable) then try to send it with the inline se

[OMPI devel] Fwd: Network change of the CREST SVN/trac server (tiger)

2014-04-08 Thread Jeff Squyres (jsquyres)
FYI. The SVN server will be rebooted Thursday; a short outage is expected. See below for details. Begin forwarded message: > From: Kim, DongInn > Subject: Network change of the CREST SVN/trac server (tiger) > Date: April 8, 2014 10:01:46 AM EDT > > Dear All, > > The CREST SVN/trac server ma

Re: [OMPI devel] Trunk is broken by PSHMEM commit

2014-04-08 Thread Roman Kotelnikov
Hello! Thanks, updated svn:ingore on oshmem folder in rev 31336. On Tue, Apr 8, 2014 at 4:36 PM, Jeff Squyres (jsquyres) wrote: > Please also update the svn:ignore properties in the oshmem tree. > > > On Apr 8, 2014, at 6:52 AM, Mike Dubman wrote: > > > thanks > > fixed here: r31334 > > > > >

Re: [OMPI devel] Trunk is broken by PSHMEM commit

2014-04-08 Thread Jeff Squyres (jsquyres)
Please also update the svn:ignore properties in the oshmem tree. On Apr 8, 2014, at 6:52 AM, Mike Dubman wrote: > thanks > fixed here: r31334 > > > On Tue, Apr 8, 2014 at 6:03 AM, Ralph Castain wrote: > On Linux, with oshmem enabled: > > pinit_f.c:26:2: warning: #ident is a GCC extension >

Re: [OMPI devel] Trunk is broken by PSHMEM commit

2014-04-08 Thread Mike Dubman
thanks fixed here: r31334 On Tue, Apr 8, 2014 at 6:03 AM, Ralph Castain wrote: > On Linux, with oshmem enabled: > > pinit_f.c:26:2: warning: #ident is a GCC extension > pshmem_init.c:31: warning: no previous prototype for 'pstart_pes' > pshmem_align.c:25: warning: no previous prototype for 'psh

Re: [OMPI devel] bitbucket mirror out of date

2014-04-08 Thread Jeff Squyres (jsquyres)
Sorry about that -- the push to bitbucket was failing because it created a new branch (v1.8). I fixed it. On Apr 8, 2014, at 3:30 AM, Guillaume Papauré wrote: > Hi, > it seems that the bitbucket mercurial mirror has not been updated since > march 25th. > Could you restart the update proces

[OMPI devel] bitbucket mirror out of date

2014-04-08 Thread Guillaume Papauré
Hi, it seems that the bitbucket mercurial mirror has not been updated since march 25th. Could you restart the update process ? Regards, Guillaume