Re: [OMPI devel] Build failures on trunk? r21235

Jeff Squyres wrote: I take that back -- I just did 3 more builds and was unable to get the VT build to fail. That's not good. :-( And I'm never getting there - I still fail in tools/orte-iof, same way. I tried removing apple's mpi.h in /usr/include, but that wasn't it. This is a very

Re: [OMPI devel] Build failures on trunk? r21235

On May 14, 2009, at 3:14 PM, Jeff Squyres (jsquyres) wrote: The Leopard build failed deep in VT, though, with some obscure C++ STL- looking error -- but OMPI itself built fine. You can compile OMPI without VT with --enable-contrib-no-build=vt. I'll send a note to the VT guys. I take that

Re: [OMPI devel] Build failures on trunk? r21235

Hmm. I just did a build with both the SF.net compilers and then a 2nd build with the native leopard compilers of openmpi-1.3.3a1r21223. The Leopard build failed deep in VT, though, with some obscure C++ STL- looking error -- but OMPI itself built fine. You can compile OMPI without VT with

Re: [OMPI devel] Build failures on trunk? r21235

On Thu, 2009-05-14 at 19:46 +0200, Ralf Wildenhues wrote: > Hello, > > Ashley, did you rebootstrap with Debian's Libtool? I'm not sure I understand the question, I did a fresh checkout and re-ran ./autogen.sh if that's what you mean. > They enable link_all_deplibs=no in their Libtool That

Re: [OMPI devel] Build failures on trunk? r21235

Jeff Squyres wrote: Did you mean to attach something? yeah, oops. I can't count how many times I've done that FWIW, I can configure/build on Leopard just fine...? I'm using the compilers from hpc.sf.net, though. I haven't tried recently with the native Leopard compilers. This was with

Re: [OMPI devel] Build failures on trunk? r21235

Blast - wish I could remember, but I did see that once before and now can't remember the fix. I can build non-tarballs just fine on my Mac, though, so it could be a problem with the tarball not picking something up. On Thu, May 14, 2009 at 12:41 PM, Bryan Lally wrote: > Argh.

Re: [OMPI devel] Build failures on trunk? r21235

Argh. This time with attachment attached ... Bryan Lally wrote: While we're talking about build failures ... I haven't been able to build any of the 1.3.x releases on my OS X machines. OS X 10.5.6 (Leopard) on Intel macs. Attached is the configure command and the failure from last night's

Re: [OMPI devel] Build failures on trunk? r21235

Did you mean to attach something? FWIW, I can configure/build on Leopard just fine...? I'm using the compilers from hpc.sf.net, though. I haven't tried recently with the native Leopard compilers. On May 14, 2009, at 2:38 PM, Bryan Lally wrote: While we're talking about build failures

Re: [OMPI devel] Build failures on trunk? r21235

While we're talking about build failures ... I haven't been able to build any of the 1.3.x releases on my OS X machines. OS X 10.5.6 (Leopard) on Intel macs. Attached is the configure command and the failure from last night's development tarball, openmpi-1.3.3a1r21223.tar.gz. 1.2.x builds

Re: [OMPI devel] Build failures on trunk? r21235

On Thu, 14 May 2009, Jeff Squyres wrote: On May 14, 2009, at 2:22 PM, Brian W. Barrett wrote: We actually took pains to *not* do that; we *used* to do that and explicitly took it out. :-\ IIRC, it had something to do with dlopen'ing libmpi.so...? Actually, I think that was something

Re: [OMPI devel] Build failures on trunk? r21235

On Thu, 14 May 2009, Ralf Wildenhues wrote: Hi Brian, * Brian W. Barrett wrote on Thu, May 14, 2009 at 08:22:58PM CEST: Actually, I think that was something else. Today, libopen-rte.la lists libopen-pal.la as a dependency and libmpi.la lists libopen-rte.la. I had removed the dependency of

Re: [OMPI devel] Build failures on trunk? r21235

On May 14, 2009, at 2:22 PM, Brian W. Barrett wrote: > We actually took pains to *not* do that; we *used* to do that and explicitly > took it out. :-\ IIRC, it had something to do with dlopen'ing libmpi.so...? Actually, I think that was something else. Today, libopen-rte.la lists

Re: [OMPI devel] Build failures on trunk? r21235

Hi Brian, * Brian W. Barrett wrote on Thu, May 14, 2009 at 08:22:58PM CEST: > > Actually, I think that was something else. Today, libopen-rte.la lists > libopen-pal.la as a dependency and libmpi.la lists libopen-rte.la. I had > removed the dependency of libmpi.la on libopen-pal.la because it

Re: [OMPI devel] Build failures on trunk? r21235

On Thu, 14 May 2009, Jeff Squyres wrote: On May 14, 2009, at 1:46 PM, Ralf Wildenhues wrote: A more permanent workaround could be in OpenMPI to list each library that is used *directly* by some other library as a dependency. Sigh. We actually took pains to *not* do that; we *used* to do

Re: [OMPI devel] Build failures on trunk? r21235

Hello, * Jeff Squyres wrote on Thu, May 14, 2009 at 07:56:24PM CEST: > On May 14, 2009, at 1:46 PM, Ralf Wildenhues wrote: > >> A more permanent workaround could be in OpenMPI to list each library >> that is used *directly* by some other library as a dependency. Sigh. > > We actually took pains

Re: [OMPI devel] Build failures on trunk? r21235

On May 14, 2009, at 1:46 PM, Ralf Wildenhues wrote: A more permanent workaround could be in OpenMPI to list each library that is used *directly* by some other library as a dependency. Sigh. We actually took pains to *not* do that; we *used* to do that and explicitly took it out. :-\

Re: [OMPI devel] Build failures on trunk? r21235

Hello, Ashley, did you rebootstrap with Debian's Libtool? They enable link_all_deplibs=no in their Libtool which changes some things and can cause issues like this. Can't hurt to open a Debian bug report about it (targeted against libtool) so they know this issue exists. Can you try working

Re: [OMPI devel] Build failures on trunk? r21235

Hmm. This may not be pilot error. I build OMPI with a pre-installed OMPI all the time and they don't conflict during the build (i.e., the building OMPI always uses the libopen-rte and libopen-pal from the build tree, not the install tree). Here's my link lines for ompi_info: /bin/sh

Re: [OMPI devel] OMPI 1.3 branch

On Thu, May 14, 2009 at 10:47 AM, Terry Dontje wrote: > Ralph Castain wrote: > >> Hi folks >> >> I encourage people to please look at your MTT outputs. As we are preparing >> to roll the 1.3.3 release, I am seeing a lot of problems on the branch: >> >> 1. timeouts, coming

Re: [OMPI devel] OMPI 1.3 branch

Ralph Castain wrote: Hi folks I encourage people to please look at your MTT outputs. As we are preparing to roll the 1.3.3 release, I am seeing a lot of problems on the branch: 1. timeouts, coming in two forms: (a) MPI_Abort hanging, and (b) collectives hanging (this is mostly on Solaris)

Re: [OMPI devel] Build failures on trunk? r21235

Libtool is 2.2.6. I use debian unstable so it's normally fairly up-to-date, I suppose it's not impossible that a debian update has broken things now that I think of it. I normally build in memfs for speed and have just rebooted my machine now, a full rebuild has failed again with the same

Re: [OMPI devel] Build failures on trunk? r21235

Hmm; odd. I'm not getting these errors. Just to be sure, I did a VPATH build and still am not getting these errors... :-\ Are those symbols publicly available in libopen-pal.so? It does seem pretty weird that your libtool link line didn't pick up libopen-rte.so and libopen-pal.so...?

[OMPI devel] OMPI 1.3 branch

Hi folks I encourage people to please look at your MTT outputs. As we are preparing to roll the 1.3.3 release, I am seeing a lot of problems on the branch: 1. timeouts, coming in two forms: (a) MPI_Abort hanging, and (b) collectives hanging (this is mostly on Solaris) 2. segfaults - mostly on

[OMPI devel] Build failures on trunk? r21235

All, After a svn update earlier I'm getting build failures on the trunk, I've tried the usual including a full clean checkout and am still getting the errors. I'm not doing anything special other than a VPATH build and this same tree build last week, it's just the update that appears to have

Re: [OMPI devel] [OMPI svn] svn:open-mpi r21234

On May 14, 2009, at 9:57 AM, Rainer Keller wrote: > This generated a bunch of warnings - the "z" length modifier is not a > generally supported option, which is why we do not use it. I see You compile with -pedantic? Ya, configure adds that automatically if you --enable-picky. >

Re: [OMPI devel] [OMPI svn] svn:open-mpi r21234

Hey Ralph, On Wednesday 13 May 2009 10:54:43 pm Ralph Castain wrote: > This generated a bunch of warnings - the "z" length modifier is not a > generally supported option, which is why we do not use it. I see You compile with -pedantic? > btl_tcp_frag.c: In function ‘mca_btl_tcp_frag_send’: >

Re: [OMPI devel] Warnings in sctp BTL

Yes, I do. All of them are on BTL_ERROR lines; I think these came in last night with the opal attribute updates. Looking at last night's MTT, those attribute changes turned up a LOT of warnings in various BTLs... Doh! On May 14, 2009, at 9:34 AM, Ralph Castain wrote: I'm not entirely

Re: [OMPI devel] Warnings in sctp BTL

Hi Jeff, On Thursday 14 May 2009 09:22:18 am Jeff Squyres wrote: > Ralph -- did these messages come in due to the opal_attribute changes > from last night? They certainly are due to adding the __opal_attribute_format__ changes. A similar patch as btl_tcp_frag should be applied... Thanks, Rainer

Re: [OMPI devel] Warnings in sctp BTL

I'm not entirely sure as I'm unclear as to when this component would attempt to build. I was building the latest trunk on a new (to me) system last night (Jeff's cluster) when I saw the warnings. Jeff: have you seen them before on your cluster? On Thu, May 14, 2009 at 7:22 AM, Jeff Squyres

Re: [OMPI devel] Warnings in sctp BTL

On May 14, 2009, at 1:14 AM, Brad Penoff wrote: At UBC, we are trying to find a new student who can maintain the SCTP BTL. Unfortunately, it is has not been maintained since the progress engine overhaul a while ago. At the moment, this is still on the TODO list. I hope to get to this myself,

Re: [OMPI devel] Warnings in sctp BTL

hey Ralph, At UBC, we are trying to find a new student who can maintain the SCTP BTL. Unfortunately, it is has not been maintained since the progress engine overhaul a while ago. At the moment, this is still on the TODO list. I hope to get to this myself, if no student is found. It was my

[OMPI devel] Warnings in sctp BTL

Hi folks Not sure who is maintaining the SCTP BTL, but I found the following warnings when building tonight: btl_sctp_frag.c: In function `mca_btl_sctp_frag_large_send': btl_sctp_frag.c:179: warning: int format, different type arg (arg 3) btl_sctp_frag.c:179: warning: int format, different