Re: [OMPI devel] [patch] man and FUNC_NAME corrections

Thanks for the patch. I applied it to the trunk in r32190, and CMR (#4780) it for the next release 1.8.2 George. On Thu, Jul 10, 2014 at 3:09 AM, Kawashima, Takahiro < t-kawash...@jp.fujitsu.com> wrote: > Hi, > > The attached patch corrects trivial typos in man files and > FUNC_NAME

[OMPI devel] [patch] man and FUNC_NAME corrections

Hi, The attached patch corrects trivial typos in man files and FUNC_NAME variables in ompi/mpi/c/*.c files. One note which may not be trivial: Before MPI-2.1, MPI standard says MPI_PACKED should be used for MPI_{Pack,Unpack}_external. But in MPI-2.1, it was changed to use MPI_BYTE. See 'B.3

Re: [OMPI devel] segv in ompi_info

Good suggestion - fixed on trunk in r32189 On Jul 9, 2014, at 2:30 PM, Paul Hargrove wrote: > I agree with Gilles that there is not a "bug", but I believe that OMPI could > do something better. > > First, I'll show that > a) this is not a new behavior > b) it is not

Re: [OMPI devel] segv in ompi_info

I agree with Gilles that there is not a "bug", but I believe that OMPI could do something better. First, I'll show that a) this is not a new behavior b) it is not limited to "less". $ (strace ompi_info -a | grep -m1 btl) 2>&1 | grep -e 'Open MPI:' -e SIGPIPE write(1, "Open MPI:

Re: [OMPI devel] Shared library version numbers for 1.8.2

Ouch - yes, we definitely should roll it to 4:0:0. I gather the ABI change was required to comply with the spec. I normally would refuse to allow an ABI change during a stable release series, but have given more latitude to OSHMEM due to its relatively new inclusion and the need to get it into

Re: [OMPI devel] Shared library version numbers for 1.8.2

Quoting "Jeff Squyres (jsquyres)" : Here's what I think VERSION should be for 1.8.2: https://svn.open-mpi.org/trac/ompi/changeset/32165 I left comments in the VERSION file as to why I think each version number should change. Can someone please verify that this work

Re: [OMPI devel] segv in ompi_info

Mike, how do you test ? i cannot reproduce a bug : if you run ompi_info -a -l 9 | less and i press 'q' at the early stage (e.g. before all output is written to the pipe) then the less process exits and receives SIG_PIPE and crash (which is a normal unix behaviour) now if i press the spacebar

Re: [OMPI devel] trunk and fortran errors

@#%$#@!$% This is almost certainly due to r32162 (Fortran commit from last night). I'm offline most of today; I won't be able to look at this until tonight at the earliest, sorry. :-( For the moment/as a workaround, use --disable-mpi-fortran in your builds if you are building with an older

Re: [OMPI devel] segv in ompi_info

mxm only intercept signals and prints the stacktrace. happens on trunk as well. only when "| less" is used. On Tue, Jul 8, 2014 at 4:50 PM, Jeff Squyres (jsquyres) wrote: > I'm unable to replicate. Please provide more detail...? Is this a > problem in the MXM

[OMPI devel] trunk and fortran errors

Hi, The latest svn/trunks fails to install on centos 5.7,5.8,5.9 but works fine on others. after: ./configure --with-platform=contrib/platform/mellanox/optimized --with-knem=/opt/knem-0.9.7mlnx1 --with-fca=/opt/mellanox/fca --with-ompi-param-check --enable-picky