Re: [OMPI devel] [v1.8] build failure with xlc-11.1

You can disregard this thread... the problem was pilot error. I understand now why the "compile" wrapper was getting used. The probe "checking whether $CC and cc understand -c and -o together... " is run WITHOUT $CFLAGS. In my case CFLAGS included an argument required to locate the compiler's co

Re: [OMPI devel] [v1.8] build failure with xlc-11.1

One note regarding my report below: I have noticed that autoconf has chosen to use "$srcdir/config/compile xlc" instead of just "xlc" (I set CC=xlc). I strongly suspect this is related, and am investigating why the compile wrapper is used. However, independent of that there does seem to be some

[OMPI devel] cosmetic configure nit

One too many 's' characters in the following: checking for asssembly architecture... -Paul -- Paul H. Hargrove phhargr...@lbl.gov Future Technologies Group Computer and Data Sciences Department Tel: +1-510-495-2352 Lawrence Berkeley National Laboratory Fax: +1-5

[OMPI devel] [v1.8] build failure with xlc-11.1

Building v1.8 nightly tarball with xlc-11.1 on a ppc64/linux platform: Making all in asm make[2]: Entering directory `/home/hargrov1/OMPI/openmpi-1.8-latest-bluedrop-64-xlc/BLD/opal/asm' CC asm.lo rm -f atomic-asm.S ln -s "../../opal/asm/generated/atomic-local.s" atomic-asm.S CPPASat

Re: [OMPI devel] [v1.8] 32-bit c++ build failure with Sun compilers

These changes also eliminate an equivalent g++ warning : /shared/OMPI/openmpi-1.8-latest-solaris11-x86-ib-gcc452/openmpi-1.8.2rc4r32480/opal/include/opal/sys/atomic.h:397:9: warning: inline function `int32_t opal_atomic_add_32(volatile int32_t*, int)' used but never defined /shared/OMPI/openmpi-1.

Re: [OMPI devel] [v1.8] 32-bit c++ build failure with Sun compilers

Kewl - thanks! On Aug 9, 2014, at 12:24 PM, Paul Hargrove wrote: > Ralph, > > Yes, that did the trick. > The attached patch applied cleanly to last night's v1.8 tarball > (1.8.2rc4r32480) and I was able to build the C++ bindings on this platform. > > -Paul > > > On Sat, Aug 9, 2014 at 7:58

Re: [OMPI devel] [v1.8] 32-bit c++ build failure with Sun compilers

Ralph, Yes, that did the trick. The attached patch applied cleanly to last night's v1.8 tarball (1.8.2rc4r32480) and I was able to build the C++ bindings on this platform. -Paul On Sat, Aug 9, 2014 at 7:58 AM, Ralph Castain wrote: > I think I chased this down - looks like it is r28034. I've a

Re: [OMPI devel] v1.8.2 still held up...

And for the record: the IA64 platform passed too. On Sat, Aug 9, 2014 at 3:22 AM, Jeff Squyres (jsquyres) wrote: > Thanks for all the testing! > > On Aug 8, 2014, at 11:21 PM, Paul Hargrove wrote: > > > > > > > > > On Thu, Aug 7, 2014 at 10:55 AM, Ralph Castain wrote: > > * fixes to coll/ml t

Re: [OMPI devel] jenkins error in trunk

r32484 On Sat, Aug 9, 2014 at 5:09 PM, Ralph Castain wrote: > Hmmmwell, I showed you how to fix them, so please feel free to do so > :-) > > I have no way to build that component. > > > On Aug 8, 2014, at 10:32 PM, Mike Dubman wrote: > > still, there are some: > > *04:58:49* coll_fca_compo

Re: [OMPI devel] [v1.8] 32-bit c++ build failure with Sun compilers

I think I chased this down - looks like it is r28034. I've attached the patch here - can you please let me know if this fixes the problem? atomics.patch Description: Binary data On Aug 8, 2014, at 11:11 PM, Paul Hargrove wrote:A problem Siegmar reported on trunk over a year an

Re: [OMPI devel] jenkins error in trunk

Hmmmwell, I showed you how to fix them, so please feel free to do so :-) I have no way to build that component. On Aug 8, 2014, at 10:32 PM, Mike Dubman wrote: > still, there are some: > > 04:58:49 coll_fca_component.c: In function 'mca_coll_fca_get_fca_lib': > 04:58:49 coll_fca_component

Re: [OMPI devel] [v1.8] java bindings build failure

Thanks Paul! On Aug 8, 2014, at 11:00 PM, Paul Hargrove wrote: > I tried /usr/java/jdk1.6.0_45 and things are fine now. > I honestly don't know if this was an Open MPI issue or a broken Java > installation. > > -Paul > > > On Fri, Aug 8, 2014 at 9:55 PM, Paul Hargrove wrote: > Ralph, > > /

Re: [OMPI devel] ORTE headers in OPAL source

Those calls should be protected with the CR FT #define - If I remember correctly. We were using the sstore to track the shared memory file names so we could clean them up on restart. I'm not sure if the sstore framework is necessary in this location, since we should be able to tell opal_crs and it

Re: [OMPI devel] ORTE headers in OPAL source

I think you're making a joke, right...? I see direct calls to ORTE sstore functionality in all three. On Aug 8, 2014, at 5:42 PM, George Bosilca wrote: > These are harmless. They are only used when FT is enabled which should rarely > be the case. > > George. > > > > On Fri, Aug 8, 201

Re: [OMPI devel] [v1.8] illegal commas after last item in enum

Fixed in trunk in r32482; CMR'ed to v1.8. Thanks. On Aug 9, 2014, at 12:36 AM, Paul Hargrove wrote: > The Solaris Studio 12.3 C++ compiler warns about commas after the last item > in an enum. > While these commas are legal in C99, they are ILLEGAL in C++ prior to C++11 > > The warnings below

Re: [OMPI devel] jenkins errors in origin/v1.8

yep, missed "green" report. Thanks On Sat, Aug 9, 2014 at 1:24 PM, Jeff Squyres (jsquyres) wrote: > Fixed with Ralph's commit last night (r32480). > > > On Aug 9, 2014, at 1:33 AM, Mike Dubman wrote: > > > 02:36:30 > > CC base/odls_base_default_fns.lo > > > > 02:36:30 > > base/odls_bas

Re: [OMPI devel] jenkins errors in origin/v1.8

Fixed with Ralph's commit last night (r32480). On Aug 9, 2014, at 1:33 AM, Mike Dubman wrote: > 02:36:30 > CC base/odls_base_default_fns.lo > > 02:36:30 > base/odls_base_default_fns.c: In function 'odls_base_default_wait_local_proc': > > 02:36:30 > base/odls_base_default_fns.c:2001

Re: [OMPI devel] v1.8.2 still held up...

Thanks for all the testing! On Aug 8, 2014, at 11:21 PM, Paul Hargrove wrote: > > > > On Thu, Aug 7, 2014 at 10:55 AM, Ralph Castain wrote: > * fixes to coll/ml that expanded to fixing page alignment in general - > someone needs to review/approve it: > https://svn.open-mpi.org/trac/

[OMPI devel] [v1.8] 32-bit c++ build failure with Sun compilers

A problem Siegmar reported on trunk over a year and a half ago is breaking a 32-bit build of the v1.8 branch with the Sun C++ compiler: Siegmar's report appears in http://www.open-mpi.org/community/lists/users/2013/01/21269.php There are several warnings, but the error is (from my current build):

Re: [OMPI devel] [v1.8] java bindings build failure

I tried /usr/java/jdk1.6.0_45 and things are fine now. I honestly don't know if this was an Open MPI issue or a broken Java installation. -Paul On Fri, Aug 8, 2014 at 9:55 PM, Paul Hargrove wrote: > Ralph, > > /usr/java/jdk1.6.0_21 > > -Paul > > > On Fri, Aug 8, 2014 at 9:51 PM, Ralph Castain

[OMPI devel] jenkins errors in origin/v1.8

*02:36:30* CC base/odls_base_default_fns.lo*02:36:30* base/odls_base_default_fns.c: In function 'odls_base_default_wait_local_proc':*02:36:30* base/odls_base_default_fns.c:2001: warning: implicit declaration of function 'ORTE_FLAG_SET'*02:36:30* base/odls_base_default_fns.c:2001: error: 'OR

Re: [OMPI devel] jenkins error in trunk

still, there are some: *04:58:49* coll_fca_component.c: In function 'mca_coll_fca_get_fca_lib':*04:58:49* coll_fca_component.c:1161: error: 'ompi_proc_t' has no member named 'proc_name'*04:58:49* coll_fca_component.c: In function 'fca_register':*04:58:49* coll_fca_component.c:1419: warning: assign

Re: [OMPI devel] [v1.8] java bindings build failure

Ralph, /usr/java/jdk1.6.0_21 -Paul On Fri, Aug 8, 2014 at 9:51 PM, Ralph Castain wrote: > This seems odd - I'm not seeing any warnings or errors when building Java. > Which JDK version do you have? > > On Aug 8, 2014, at 9:31 PM, Paul Hargrove wrote: > > Below are errors from trying tonight'

Re: [OMPI devel] [v1.8] java bindings build failure

This seems odd - I'm not seeing any warnings or errors when building Java. Which JDK version do you have? On Aug 8, 2014, at 9:31 PM, Paul Hargrove wrote: > Below are errors from trying tonight's v1.8 tarball on one of the few systems > I have access to with java. The trunk has the same error

[OMPI devel] [v1.8] illegal commas after last item in enum

The Solaris Studio 12.3 C++ compiler warns about commas after the last item in an enum. While these commas are legal in C99, they are ILLEGAL in C++ prior to C++11 The warnings below list the four instances I encountered while building the C++ bindings, but there might be others. -Paul "openmpi-

[OMPI devel] [v1.8] java bindings build failure

Below are errors from trying tonight's v1.8 tarball on one of the few systems I have access to with java. The trunk has the same errors but with all the line numbers increased by exactly 18. -Paul Making all in java make[3]: Entering directory `/brashear/hargrove/OMPI/openmpi-1.8-latest-linux-x8