[OMPI devel] openmpi-1.5.5rc1 (re)tested on non-linux platforms

2011-12-16 Thread Paul H. Hargrove
I said I didn't have the patience to retest until rc2, but a bit of scripting has changed that. It not only gave me the patience to re-test, but to expand my testing to 15 non-linux machines. I've tested the 1.5.5rc1 tarball on a pile of non-linix systems with 2 fixes in place: + Added #incl

[OMPI devel] GNU Make required for OMPI 1.5.5rc1: known/intended?

2011-12-16 Thread Paul H. Hargrove
I've noticed that on, for instance, FreeBSD I must compile openmpi-1.5.5rc1 with "gmake" rather than "make". I didn't see "GNU Make" listed as a build dependency in the README, and so I wonder if this was known. The failure mode seen with Berkeley Make in place of GNU Make is somewhat non-intu

Re: [OMPI devel] MPIR attach from padb broken (1.5.5rc1)

2011-12-16 Thread Jeff Squyres
On Dec 16, 2011, at 10:56 AM, Nathan T. Hjelm wrote: >> Why do the symbols need to be weak? Remember that not all platforms >> support weak symbols. > > I don't know. The way we currently pull MPIR symbols into orterun breaks > with some configuration. If we don't pull the symbols in then launch

Re: [OMPI devel] MPIR attach from padb broken (1.5.5rc1)

2011-12-16 Thread Nathan T. Hjelm
> Why do the symbols need to be weak? Remember that not all platforms > support weak symbols. I don't know. The way we currently pull MPIR symbols into orterun breaks with some configuration. If we don't pull the symbols in then launchmon can't attach to orterun. Moving the symbols to weak fixes

Re: [OMPI devel] MPIR attach from padb broken (1.5.5rc1)

2011-12-16 Thread Jeff Squyres
Why do the symbols need to be weak? Remember that not all platforms support weak symbols. The symbols don't need to be in the executable itself, right? It should be fine for them to be a library (e.g., libopen-rte.so/a). On Dec 16, 2011, at 4:51 AM, Ashley Pittman wrote: > > Yes, this fixe

Re: [OMPI devel] Retrying a MPI_SEND

2011-12-16 Thread George Bosilca
Setting the error handler to MPI_ERRORS_RETURN is the right solution for mechanism using the PMPI interface. Hugo is one software layer below the MPI interface, so the error handler is not affecting his code. However, once he reacts to an error, he should reset the error (in the status attached

Re: [OMPI devel] Retrying a MPI_SEND

2011-12-16 Thread Jeff Squyres
I'm jumping into the middle of this conversation and probably don't have all the right context, so forgive me if this is a stupid question: did you set MPI_ERRORS_RETURN on the communicator in question? On Dec 14, 2011, at 10:43 AM, Hugo Daniel Meyer wrote: > Hello George and @ll. > > Sorry f

Re: [OMPI devel] MPIR attach from padb broken (1.5.5rc1)

2011-12-16 Thread Ashley Pittman
Yes, this fixes the issue. Ashley. On 15 Dec 2011, at 23:42, Nathan Hjelm wrote: > I have an idea. How about we set those the MPIR variables as weak. Just > tested it with STAT. > > Can you replace orte/tools/orterun/orterun.c with the attached version and > see if it fixes the issue? > > -