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] My MPI build is broke, don't know why/how

2012-08-23 Thread Ralph Castain
The 1.6 code always expects to find the default hostfile, even if it is empty. We always install it by default, so I don't know why yours isn't there. In the future, we just ignore it if we don't find it. You have two options: 1. create that file and leave it empty 2. you can work around it by

[OMPI users] My MPI build is broke, don't know why/how

2012-08-23 Thread Jim Kusznir
Hi all: I recently rebuilt my cluster from rocks 5 to rocks 6 (which is based on CentOS 6.2) using the official spec file and my build options as before. It all built successfully and all appeared good. That is, until one tried to use it. This is built with torque integration, and its run throu

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] pax glitch when building on Tsubame 2.0

2012-08-23 Thread Reuti
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 24.08.2012 um 00:13 schrieb Andreas Schäfer: > On 00:05 Fri 24 Aug , Reuti wrote: >> Am 23.08.2012 um 23:28 schrieb Andreas Schäfer: >> >>> ... >>> checking for style of include used by make... GNU >>> checking how to create a ustar tar archiv

Re: [OMPI users] pax glitch when building on Tsubame 2.0

2012-08-23 Thread Andreas Schäfer
Hi, On 00:05 Fri 24 Aug , Reuti wrote: > Am 23.08.2012 um 23:28 schrieb Andreas Schäfer: > > > ... > > checking for style of include used by make... GNU > > checking how to create a ustar tar archive... > > ATTENTION! pax archive volume change required. > > Ready for archive volume: 1 > > In

Re: [OMPI users] pax glitch when building on Tsubame 2.0

2012-08-23 Thread Reuti
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Am 23.08.2012 um 23:28 schrieb Andreas Schäfer: > ... > checking for style of include used by make... GNU > checking how to create a ustar tar archive... > ATTENTION! pax archive volume change required. > Ready for archive volume: 1 > Input arch

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

[OMPI users] pax glitch when building on Tsubame 2.0

2012-08-23 Thread Andreas Schäfer
Hi, I noticed that pax will ask me for an archive name when I run configure on Tsubame 2.0 (log see below). It doesn't break the build (I can just enter a dot to quit pax), but I thought I might just as well report it as it put me off and I feel this isn't the expected behavior. I don't see this o