Re: [OMPI users] PG compilers and OpenMPI 1.6.1

2012-08-27 Thread Lloyd Brown
Thanks for getting this in so quickly. Yes, the nightly tarball from Aug 25 (a1r27142), seems to get through a configure and make stage at least. Thanks, Lloyd Brown Systems Administrator Fulton Supercomputing Lab Brigham Young University http://marylou.byu.edu On 08/25/2012 05:18 AM, Jeff Squy

Re: [OMPI users] PG compilers and OpenMPI 1.6.1

2012-08-25 Thread Jeff Squyres
I've merged the VT fix into the 1.6 branch; it will be available in tonight's tarball. Can you give a nightly v1.6 tarball a whirl to ensure it fixes your problem? http://www.open-mpi.org/nightly/v1.6/ On Aug 23, 2012, at 7:30 PM, Jeff Squyres (jsquyres) wrote: > Yes. VT = vampirtrace. >

Re: [OMPI users] PG compilers and OpenMPI 1.6.1

2012-08-23 Thread Jeff Squyres (jsquyres)
Yes. VT = vampirtrace. Sent from my phone. No type good. On Aug 23, 2012, at 6:49 PM, "Lloyd Brown" wrote: > Okay. Sounds good. I'll watch that bug. > > For my own sanity check, "vt" means VampirTrace stuff, right? In our > environment, I don't think it'll be a problem to disable VampirTr

Re: [OMPI users] PG compilers and OpenMPI 1.6.1

2012-08-23 Thread Lloyd Brown
Okay. Sounds good. I'll watch that bug. For my own sanity check, "vt" means VampirTrace stuff, right? In our environment, I don't think it'll be a problem to disable VampirTrace temporarily. More people here use the Intel and GNU compiled versions anyway, both of which compile just fine with 1

Re: [OMPI users] PG compilers and OpenMPI 1.6.1

2012-08-23 Thread Jeff Squyres
This was reported earlier today: https://svn.open-mpi.org/trac/ompi/ticket/3251 I've alerted the VT guys to have a look. For a workaround, you can --disable-vt. On Aug 23, 2012, at 6:00 PM, Ralph Castain wrote: > Just looking at your output, it looks like there is a missing header that P

Re: [OMPI users] PG compilers and OpenMPI 1.6.1

2012-08-23 Thread Ralph Castain
Just looking at your output, it looks like there is a missing header that PGI requires - I have no idea what that might be. You might do a search for omp_lock_t to see where it is defined and add that head to the vt_wrapper.cc file and see if that fixes the problem On Aug 23, 2012, at 2:44 PM,

[OMPI users] PG compilers and OpenMPI 1.6.1

2012-08-23 Thread Lloyd Brown
Has anyone been able to get OpenMPI 1.6.1 to compile with a recent Portland Group compiler set? I'm currently trying on RHEL 6.2 with PG compilers v12.5 (2012), and I keep getting errors like the ones below. It could easily be a problem with the compiler code, but since this doesn't happen with Op