Re: [OMPI devel] 1.7.4rc2r30148 run failure NetBSD6-x86

Hey Paul, Thanks for report, we will commit fix shortly. M On Fri, Jan 10, 2014 at 7:20 AM, Paul Hargrove wrote: > > On Thu, Jan 9, 2014 at 9:05 PM, Ralph Castain wrote: > >> Not sure why the shmem fortran examples would try to build - will pass >> that

Re: [OMPI devel] 1.7.4rc2r30148 run failure NetBSD6-x86

On Thu, Jan 9, 2014 at 9:05 PM, Ralph Castain wrote: > Not sure why the shmem fortran examples would try to build - will pass > that off to Jeff as well (sorry Jeff!) This is the issue I described in http://www.open-mpi.org/community/lists/devel/2014/01/13616.php It seems

Re: [OMPI devel] 1.7.4rc2r30148 run failure NetBSD6-x86

Really have to thank you for your persistence, Paul. Truly appreciated. Glad to hear you can run ring_c. I'm going to let Jeff handle the path.c and ANON issue as those are both configury things he was working today. Not sure why the shmem fortran examples would try to build - will pass that

Re: [OMPI devel] 1.7.4rc2r30148 run failure NetBSD6-x86

Ralph, My NetBSD builds fail on the new opal/util/path.c, but by adding #undef HAVE_STATFS near the top of path.c I can get past that. Next I hit the MAP_ANON-vs-MAP_ANONYMOUS issue and fixed that manually. Next I hit the attempt to build shmem fortran examples despite the lack of a fortran

Re: [OMPI devel] 1.7.4rc2r30148 run failure NetBSD6-x86

Many thanks, Paul! On Jan 9, 2014, at 3:07 PM, Paul Hargrove wrote: > Ralph, > > Thanks for fielding all these issues I've been finding. > I will plan to run tonight's trunk tarball through all of the systems where > I've seen any issues. > > -Paul > > > On Thu, Jan 9,

Re: [OMPI devel] 1.7.4rc2r30148 run failure NetBSD6-x86

Ralph, Thanks for fielding all these issues I've been finding. I will plan to run tonight's trunk tarball through all of the systems where I've seen any issues. -Paul On Thu, Jan 9, 2014 at 8:40 AM, Ralph Castain wrote: > Should now be fixed in trunk (silently fall back to

Re: [OMPI devel] 1.7.4rc2r30148 run failure NetBSD6-x86

Should now be fixed in trunk (silently fall back to not binding if cores not found) - scheduled for 1.7.4. If you could test the next trunk tarball, that would help as I can't actually test it on my machines On Jan 9, 2014, at 6:25 AM, Ralph Castain wrote: > I see the

Re: [OMPI devel] 1.7.4rc2r30148 run failure NetBSD6-x86

I see the issue - there are no "cores" on this topology, only "pu's", so "bind-to core" is going to fail even though binding is supported. Will adjust. Thanks! On Jan 8, 2014, at 9:06 PM, Paul Hargrove wrote: > Requested verbose output below. > -Paul > > -bash-4.2$ mpirun

Re: [OMPI devel] 1.7.4rc2r30148 run failure NetBSD6-x86

Requested verbose output below. -Paul -bash-4.2$ mpirun -mca ess_base_verbose 10 -np 1 examples/ring_c [pcp-j-17:02150] mca: base: components_register: registering ess components [pcp-j-17:02150] mca: base: components_register: found loaded component env [pcp-j-17:02150] mca: base:

Re: [OMPI devel] 1.7.4rc2r30148 run failure NetBSD6-x86

Hmmm...looks to me like the code should protect against this - unless the system isn't correctly reporting binding support. Could you run this with "-mca ess_base_verbose 10"? This will output the topology we found, including the binding support (which isn't in the usual output). On Jan 8,

Re: [OMPI devel] 1.7.4rc2r30148 run failure NetBSD6-x86

Hmmm...I see the problem. Looks like binding isn't supported on that system for some reason, so we need to turn "off" our auto-binding when we hit that condition. I'll check to see why that isn't happening (was supposed to do so) On Jan 8, 2014, at 3:43 PM, Paul Hargrove

[OMPI devel] 1.7.4rc2r30148 run failure NetBSD6-x86

While I have yet to get a working build on NetBSD for x86-64 h/w, I *have* successfully built Open MPI's current 1.7.4rc tarball on NetBSD-6 for x86. However, I can't *run* anything: Attempting the ring_c example on 2 cores: -bash-4.2$ mpirun -mca btl sm,self -np 2 examples/ring_c