date:20140809

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
config files and consequently the probe failed.  I consider that "pilot
error" on my part and have moved the config option to the definition of CC
instead (and the problem goes away)

So, while there *may* exist some valid set of conditions under which the
current configure/build could produce the reported failure, my test did NOT
represent a valid set of conditions.

-Paul


On Sat, Aug 9, 2014 at 1:29 PM, Paul Hargrove  wrote:

> 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 flaw in how the atomics are
> getting built on this configuration.
>
> -Paul
>
>
> On Sat, Aug 9, 2014 at 1:22 PM, Paul Hargrove  wrote:
>
>> 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
>>   CPPASatomic-asm.lo
>>   CCLD libasm.la
>> ar: .libs/atomic-asm.o: No such file or directory
>>
>> The related portion of the configure output:
>>
>> *** Assembler
>> checking dependency style of
>> /home/hargrov1/OMPI/openmpi-1.8-latest-bluedrop-64-xlc/openmpi-1.8.2rc4r32480/config/compile
>> xlc... none
>> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
>> checking the name lister (/usr/bin/nm -B) interface... BSD nm
>> checking for fgrep... /bin/grep -F
>> checking if need to remove -g from CCASFLAGS... no
>> checking whether to enable smp locks... yes
>> checking if .proc/endp is needed... no
>> checking directive for setting text section... .text
>> checking directive for exporting symbols... .globl
>> checking for objdump... objdump
>> checking if .note.GNU-stack is needed... no
>> checking suffix for labels... :
>> checking prefix for global symbol labels...
>> checking prefix for lsym labels... .L
>> checking prefix for function in .type... @
>> checking if .size is needed... yes
>> checking if .align directive takes logarithmic value... yes
>> checking if PowerPC registers have r prefix... no
>> checking if
>> /home/hargrov1/OMPI/openmpi-1.8-latest-bluedrop-64-xlc/openmpi-1.8.2rc4r32480/config/compile
>> xlc supports GCC inline assembly... yes
>> checking if
>> /home/hargrov1/OMPI/openmpi-1.8-latest-bluedrop-64-xlc/openmpi-1.8.2rc4r32480/config/compile
>> xlc supports DEC inline assembly... no
>> checking if
>> /home/hargrov1/OMPI/openmpi-1.8-latest-bluedrop-64-xlc/openmpi-1.8.2rc4r32480/config/compile
>> xlc supports XLC inline assembly... no
>> checking for assembly format... default-.text-.globl-:--.L-@-1-1-0-1-0
>> checking for asssembly architecture... POWERPC64
>> checking for builtin atomics... BUILTIN_NO
>> checking for perl... perl
>> checking for pre-built assembly file... no (not in asm-data)
>> checking whether possible to generate assembly file... yes
>> checking for atomic assembly filename... atomic-local.s
>>
>> -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-510-486-6900
>>
>
>
>
> --
> 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-510-486-6900
>



-- 
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-510-486-6900

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 flaw in how the atomics are getting
built on this configuration.

-Paul


On Sat, Aug 9, 2014 at 1:22 PM, Paul Hargrove  wrote:

> 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
>   CPPASatomic-asm.lo
>   CCLD libasm.la
> ar: .libs/atomic-asm.o: No such file or directory
>
> The related portion of the configure output:
>
> *** Assembler
> checking dependency style of
> /home/hargrov1/OMPI/openmpi-1.8-latest-bluedrop-64-xlc/openmpi-1.8.2rc4r32480/config/compile
> xlc... none
> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
> checking the name lister (/usr/bin/nm -B) interface... BSD nm
> checking for fgrep... /bin/grep -F
> checking if need to remove -g from CCASFLAGS... no
> checking whether to enable smp locks... yes
> checking if .proc/endp is needed... no
> checking directive for setting text section... .text
> checking directive for exporting symbols... .globl
> checking for objdump... objdump
> checking if .note.GNU-stack is needed... no
> checking suffix for labels... :
> checking prefix for global symbol labels...
> checking prefix for lsym labels... .L
> checking prefix for function in .type... @
> checking if .size is needed... yes
> checking if .align directive takes logarithmic value... yes
> checking if PowerPC registers have r prefix... no
> checking if
> /home/hargrov1/OMPI/openmpi-1.8-latest-bluedrop-64-xlc/openmpi-1.8.2rc4r32480/config/compile
> xlc supports GCC inline assembly... yes
> checking if
> /home/hargrov1/OMPI/openmpi-1.8-latest-bluedrop-64-xlc/openmpi-1.8.2rc4r32480/config/compile
> xlc supports DEC inline assembly... no
> checking if
> /home/hargrov1/OMPI/openmpi-1.8-latest-bluedrop-64-xlc/openmpi-1.8.2rc4r32480/config/compile
> xlc supports XLC inline assembly... no
> checking for assembly format... default-.text-.globl-:--.L-@-1-1-0-1-0
> checking for asssembly architecture... POWERPC64
> checking for builtin atomics... BUILTIN_NO
> checking for perl... perl
> checking for pre-built assembly file... no (not in asm-data)
> checking whether possible to generate assembly file... yes
> checking for atomic assembly filename... atomic-local.s
>
> -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-510-486-6900
>



-- 
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-510-486-6900

[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-510-486-6900

[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
CPPASatomic-asm.lo
CCLD libasm.la
ar: .libs/atomic-asm.o: No such file or directory

The related portion of the configure output:

*** Assembler
checking dependency style of
/home/hargrov1/OMPI/openmpi-1.8-latest-bluedrop-64-xlc/openmpi-1.8.2rc4r32480/config/compile
xlc... none
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking for fgrep... /bin/grep -F
checking if need to remove -g from CCASFLAGS... no
checking whether to enable smp locks... yes
checking if .proc/endp is needed... no
checking directive for setting text section... .text
checking directive for exporting symbols... .globl
checking for objdump... objdump
checking if .note.GNU-stack is needed... no
checking suffix for labels... :
checking prefix for global symbol labels...
checking prefix for lsym labels... .L
checking prefix for function in .type... @
checking if .size is needed... yes
checking if .align directive takes logarithmic value... yes
checking if PowerPC registers have r prefix... no
checking if
/home/hargrov1/OMPI/openmpi-1.8-latest-bluedrop-64-xlc/openmpi-1.8.2rc4r32480/config/compile
xlc supports GCC inline assembly... yes
checking if
/home/hargrov1/OMPI/openmpi-1.8-latest-bluedrop-64-xlc/openmpi-1.8.2rc4r32480/config/compile
xlc supports DEC inline assembly... no
checking if
/home/hargrov1/OMPI/openmpi-1.8-latest-bluedrop-64-xlc/openmpi-1.8.2rc4r32480/config/compile
xlc supports XLC inline assembly... no
checking for assembly format... default-.text-.globl-:--.L-@-1-1-0-1-0
checking for asssembly architecture... POWERPC64
checking for builtin atomics... BUILTIN_NO
checking for perl... perl
checking for pre-built assembly file... no (not in asm-data)
checking whether possible to generate assembly file... yes
checking for atomic assembly filename... atomic-local.s

-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-510-486-6900

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.8-latest-solaris11-x86-ib-gcc452/openmpi-1.8.2rc4r32480/opal/include/opal/sys/atomic.h:407:9:
warning: inline function `int32_t opal_atomic_sub_32(volatile int32_t*,
int)' used but never defined

-Paul



On Sat, Aug 9, 2014 at 12:36 PM, Ralph Castain  wrote:

> 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 AM, Ralph Castain  wrote:
>
>> 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?
>>
>>
>>
>> On Aug 8, 2014, at 11:11 PM, Paul Hargrove  wrote:
>>
>> 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):
>>
>>
>> "/shared/OMPI/openmpi-1.8-latest-solaris11-x86-ib-ss12u3/openmpi-1.8.2rc4r32480/ompi/mpi/cxx/
>> file.cc", Error: The function opal_atomic_add_32(volatile int*, int) has
>> not had a body defined.
>>
>> Brian attached a possible fix to
>> http://www.open-mpi.org/community/lists/users/2013/01/21272.php
>> It applies cleanly to v1.8 but appears to make things worse, trading that
>> one error for two:
>>
>> "/shared/OMPI/openmpi-1.8-latest-solaris11-x86-ib-ss12u3/openmpi-1.8.2rc4r32480/opal/include/opal/sys/atomic_impl.h",
>> line 106: Error: opal_atomic_add_64(volatile long long*, long long) was
>> previously declared "extern", not "inline".
>> "/shared/OMPI/openmpi-1.8-latest-solaris11-x86-ib-ss12u3/openmpi-1.8.2rc4r32480/opal/include/opal/sys/atomic_impl.h",
>> line 121: Error: opal_atomic_sub_64(volatile long long*, long long) was
>> previously declared "extern", not "inline".
>>
>>
>> The good news is that the problem does not exist on the trunk.
>> So, hopefully somebody can track down the proper changes to CMR.
>>
>> -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-510-486-6900
>>  ___
>> devel mailing list
>> de...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> Link to this post:
>> http://www.open-mpi.org/community/lists/devel/2014/08/15582.php
>>
>>
>>
>> ___
>> devel mailing list
>> de...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> Link to this post:
>> http://www.open-mpi.org/community/lists/devel/2014/08/15591.php
>>
>
>
>
> --
> 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-510-486-6900
>  ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/08/15594.php
>
>
>
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/08/15595.php
>



-- 
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-510-486-6900

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 AM, Ralph Castain  wrote:
> 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?
> 
> 
> 
> On Aug 8, 2014, at 11:11 PM, Paul Hargrove  wrote:
> 
>> 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):
>> 
>> "/shared/OMPI/openmpi-1.8-latest-solaris11-x86-ib-ss12u3/openmpi-1.8.2rc4r32480/ompi/mpi/cxx/file.cc",
>>  Error: The function opal_atomic_add_32(volatile int*, int) has not had a 
>> body defined.
>> 
>> Brian attached a possible fix to 
>> http://www.open-mpi.org/community/lists/users/2013/01/21272.php
>> It applies cleanly to v1.8 but appears to make things worse, trading that 
>> one error for two:
>> 
>> "/shared/OMPI/openmpi-1.8-latest-solaris11-x86-ib-ss12u3/openmpi-1.8.2rc4r32480/opal/include/opal/sys/atomic_impl.h",
>>  line 106: Error: opal_atomic_add_64(volatile long long*, long long) was 
>> previously declared "extern", not "inline".
>> "/shared/OMPI/openmpi-1.8-latest-solaris11-x86-ib-ss12u3/openmpi-1.8.2rc4r32480/opal/include/opal/sys/atomic_impl.h",
>>  line 121: Error: opal_atomic_sub_64(volatile long long*, long long) was 
>> previously declared "extern", not "inline".
>> 
>> 
>> The good news is that the problem does not exist on the trunk.
>> So, hopefully somebody can track down the proper changes to CMR.
>> 
>> -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-510-486-6900
>> ___
>> devel mailing list
>> de...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> Link to this post: 
>> http://www.open-mpi.org/community/lists/devel/2014/08/15582.php
> 
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/08/15591.php
> 
> 
> 
> -- 
> 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-510-486-6900
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/08/15594.php

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 attached the
> patch here - can you please let me know if this fixes the problem?
>
>
>
> On Aug 8, 2014, at 11:11 PM, Paul Hargrove  wrote:
>
> 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):
>
>
> "/shared/OMPI/openmpi-1.8-latest-solaris11-x86-ib-ss12u3/openmpi-1.8.2rc4r32480/ompi/mpi/cxx/
> file.cc", Error: The function opal_atomic_add_32(volatile int*, int) has
> not had a body defined.
>
> Brian attached a possible fix to
> http://www.open-mpi.org/community/lists/users/2013/01/21272.php
> It applies cleanly to v1.8 but appears to make things worse, trading that
> one error for two:
>
> "/shared/OMPI/openmpi-1.8-latest-solaris11-x86-ib-ss12u3/openmpi-1.8.2rc4r32480/opal/include/opal/sys/atomic_impl.h",
> line 106: Error: opal_atomic_add_64(volatile long long*, long long) was
> previously declared "extern", not "inline".
> "/shared/OMPI/openmpi-1.8-latest-solaris11-x86-ib-ss12u3/openmpi-1.8.2rc4r32480/opal/include/opal/sys/atomic_impl.h",
> line 121: Error: opal_atomic_sub_64(volatile long long*, long long) was
> previously declared "extern", not "inline".
>
>
> The good news is that the problem does not exist on the trunk.
> So, hopefully somebody can track down the proper changes to CMR.
>
> -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-510-486-6900
>  ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/08/15582.php
>
>
>
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/08/15591.php
>



-- 
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-510-486-6900

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 that expanded to fixing page alignment in general -
> someone needs to review/approve it:
> > https://svn.open-mpi.org/trac/ompi/ticket/4826
> >
> > I've been able to confirm that the nightly tarball (1.8.2rc4r32480)
> works as expected on the SPARC and PPC64 platforms where I had reproduced
> the problem previously.  I won't have access to the IA64 platform (which
> also has pagesize != 4K) until about 6 hours from now, but have no doubt
> the fix will work there too.
> >
> > -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-510-486-6900
> > ___
> > devel mailing list
> > de...@open-mpi.org
> > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> > Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/08/15574.php
>
>
> --
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
>
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/08/15583.php
>



-- 
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-510-486-6900

Re: [OMPI devel] jenkins error in trunk

2014-08-09 Thread Mike Dubman

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_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: 
> assignment discards qualifiers from pointer target type*04:58:49* make[2]: 
> *** [coll_fca_component.lo] Error 1*04:58:49* make[2]: Leaving directory 
> `/scrap/jenkins/scrap/workspace/hpc-ompi-shmem-3/label/hpc-test-node/ompi/mca/coll/fca'
>
>
>
> On Fri, Aug 8, 2014 at 7:12 PM, Ralph Castain  wrote:
>
>> Fixed in r32462
>>
>> On Aug 8, 2014, at 8:13 AM, Mike Dubman  wrote:
>>
>>
>>  *Josh,Devendar - could you please take a look?*
>>
>> *Thanks*
>>
>>
>> *15:45:00* Making install in mca/coll/fca*15:45:00* make[2]: Entering 
>> directory 
>> `/scrap/jenkins/scrap/workspace/hpc-ompi-shmem/label/hpc-test-node/ompi/mca/coll/fca'*15:45:00*
>>CC   coll_fca_module.lo*15:45:00* coll_fca_module.c: In function 
>> 'have_remote_peers':*15:45:00* coll_fca_module.c:48: error: 'ompi_proc_t' 
>> has no member named 'proc_flags'*15:45:00* coll_fca_module.c:48: error: 
>> 'ompi_proc_t' has no member named 'proc_flags'*15:45:00* coll_fca_module.c: 
>> In function '__get_local_ranks':*15:45:00* coll_fca_module.c:75: error: 
>> 'ompi_proc_t' has no member named 'proc_flags'*15:45:00* 
>> coll_fca_module.c:75: error: 'ompi_proc_t' has no member named 
>> 'proc_flags'*15:45:00* coll_fca_module.c:95: error: 'ompi_proc_t' has no 
>> member named 'proc_flags'*15:45:00* coll_fca_module.c:95: error: 
>> 'ompi_proc_t' has no member named 'proc_flags'*15:45:00* make[2]: *** 
>> [coll_fca_module.lo] Error 1*15:45:00* make[2]: Leaving directory 
>> `/scrap/jenkins/scrap/workspace/hpc-ompi-shmem/label/hpc-test-node/ompi/mca/coll/fca'*15:45:00*
>>  make[1]: *** [install-recursive] Error 1*15:45:00* make[1]: Leaving 
>> directory 
>> `/scrap/jenkins/scrap/workspace/hpc-ompi-shmem/label/hpc-test-node/ompi'*15:45:00*
>>  make: *** [install-recursive] Error 1*15:45:00* Build step 'Execute shell' 
>> marked build as failu
>>
>> ___
>> devel mailing list
>> de...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> Link to this post:
>> http://www.open-mpi.org/community/lists/devel/2014/08/15557.php
>>
>>
>>
>> ___
>> devel mailing list
>> de...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> Link to this post:
>> http://www.open-mpi.org/community/lists/devel/2014/08/15558.php
>>
>
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/08/15579.php
>
>
>
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/08/15590.php
>

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 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):"/shared/OMPI/openmpi-1.8-latest-solaris11-x86-ib-ss12u3/openmpi-1.8.2rc4r32480/ompi/mpi/cxx/file.cc", Error: The function opal_atomic_add_32(volatile int*, int) has not had a body defined.
Brian attached a possible fix to http://www.open-mpi.org/community/lists/users/2013/01/21272.phpIt applies cleanly to v1.8 but appears to make things worse, trading that one error for two:
"/shared/OMPI/openmpi-1.8-latest-solaris11-x86-ib-ss12u3/openmpi-1.8.2rc4r32480/opal/include/opal/sys/atomic_impl.h", line 106: Error: opal_atomic_add_64(volatile long long*, long long) was previously declared "extern", not "inline".
"/shared/OMPI/openmpi-1.8-latest-solaris11-x86-ib-ss12u3/openmpi-1.8.2rc4r32480/opal/include/opal/sys/atomic_impl.h", line 121: Error: opal_atomic_sub_64(volatile long long*, long long) was previously declared "extern", not "inline".
The good news is that the problem does not exist on the trunk.So, hopefully somebody can track down the proper changes to CMR.-Paul
-- Paul H. Hargrove                          phhargr...@lbl.govFuture Technologies Group
Computer and Data Sciences Department     Tel: +1-510-495-2352Lawrence Berkeley National Laboratory     Fax: +1-510-486-6900

___devel mailing listde...@open-mpi.orgSubscription: http://www.open-mpi.org/mailman/listinfo.cgi/develLink to this post: http://www.open-mpi.org/community/lists/devel/2014/08/15582.php

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.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: assignment discards qualifiers 
> from pointer target type
> 04:58:49 make[2]: *** [coll_fca_component.lo] Error 1
> 04:58:49 make[2]: Leaving directory 
> `/scrap/jenkins/scrap/workspace/hpc-ompi-shmem-3/label/hpc-test-node/ompi/mca/coll/fca'
> 
> 
> On Fri, Aug 8, 2014 at 7:12 PM, Ralph Castain  wrote:
> Fixed in r32462
> 
> On Aug 8, 2014, at 8:13 AM, Mike Dubman  wrote:
> 
>> 
>> Josh,Devendar - could you please take a look?
>> Thanks
>> 
>> 15:45:00 Making install in mca/coll/fca
>> 15:45:00 make[2]: Entering directory 
>> `/scrap/jenkins/scrap/workspace/hpc-ompi-shmem/label/hpc-test-node/ompi/mca/coll/fca'
>> 15:45:00   CC   coll_fca_module.lo
>> 15:45:00 coll_fca_module.c: In function 'have_remote_peers':
>> 15:45:00 coll_fca_module.c:48: error: 'ompi_proc_t' has no member named 
>> 'proc_flags'
>> 15:45:00 coll_fca_module.c:48: error: 'ompi_proc_t' has no member named 
>> 'proc_flags'
>> 15:45:00 coll_fca_module.c: In function '__get_local_ranks':
>> 15:45:00 coll_fca_module.c:75: error: 'ompi_proc_t' has no member named 
>> 'proc_flags'
>> 15:45:00 coll_fca_module.c:75: error: 'ompi_proc_t' has no member named 
>> 'proc_flags'
>> 15:45:00 coll_fca_module.c:95: error: 'ompi_proc_t' has no member named 
>> 'proc_flags'
>> 15:45:00 coll_fca_module.c:95: error: 'ompi_proc_t' has no member named 
>> 'proc_flags'
>> 15:45:00 make[2]: *** [coll_fca_module.lo] Error 1
>> 15:45:00 make[2]: Leaving directory 
>> `/scrap/jenkins/scrap/workspace/hpc-ompi-shmem/label/hpc-test-node/ompi/mca/coll/fca'
>> 15:45:00 make[1]: *** [install-recursive] Error 1
>> 15:45:00 make[1]: Leaving directory 
>> `/scrap/jenkins/scrap/workspace/hpc-ompi-shmem/label/hpc-test-node/ompi'
>> 15:45:00 make: *** [install-recursive] Error 1
>> 15:45:00 Build step 'Execute shell' marked build as failu
>> ___
>> devel mailing list
>> de...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> Link to this post: 
>> http://www.open-mpi.org/community/lists/devel/2014/08/15557.php
> 
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/08/15558.php
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/08/15579.php

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,
> 
> /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'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-x86_64-java/BLD/ompi/mpi/java/java'
>>   JAVAC  MPI.class
>> /usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:92:
>>  type parameters of T cannot be determined; no unique maximal instance 
>> exists for type variable T with upper bounds T,mpi.Struct.Data
>> return newData(buffer, 0);
>>   ^
>> /usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:107:
>>  type parameters of T cannot be determined; no unique maximal instance 
>> exists for type variable T with upper bounds T,mpi.Struct.Data
>> return newData(buffer, index * extent);
>>   ^
>> /usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:120:
>>  type parameters of T cannot be determined; no unique maximal instance 
>> exists for type variable T with upper bounds T,mpi.Struct.Data
>> return getData(buffer);
>>   ^
>> /usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:136:
>>  type parameters of T cannot be determined; no unique maximal instance 
>> exists for type variable T with upper bounds T,mpi.Struct.Data
>> return getData(buffer, index);
>>   ^
>> /usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:722:
>>  type parameters of T cannot be determined; no unique maximal instance 
>> exists for type variable T with upper bounds D,mpi.Struct.Data
>> return s.newData(buffer, offset + field);
>> ^
>> /usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:737:
>>  type parameters of T cannot be determined; no unique maximal instance 
>> exists for type variable T with upper bounds D,mpi.Struct.Data
>> return s.newData(buffer, offset + field + index * s.extent);
>> ^
>> 6 errors
>> 
>> 
>> 
>> -- 
>> 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-510-486-6900
>> ___
>> devel mailing list
>> de...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> Link to this post: 
>> http://www.open-mpi.org/community/lists/devel/2014/08/15575.php
> 
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/08/15577.php
> 
> 
> 
> -- 
> 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-510-486-6900
> 
> 
> 
> -- 
> 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-510-486-6900
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/08/15581.php

Re: [OMPI devel] ORTE headers in OPAL source

2014-08-09 Thread Josh Hursey

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 will do the right thing. I can
try to look at it early next week if someone doesn't get to it before then.

-- Josh



On Sat, Aug 9, 2014 at 7:06 AM, Jeff Squyres (jsquyres) 
wrote:

> 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, 2014 at 4:36 PM, Jeff Squyres (jsquyres) <
> jsquy...@cisco.com> wrote:
> > Here's a few ORTE headers in OPAL source -- can respective owners clean
> these up?  Thanks.
> >
> > -
> > mca/btl/smcuda/btl_smcuda.c
> > 63:#include "orte/mca/sstore/sstore.h"
> >
> > mca/btl/sm/btl_sm.c
> > 62:#include "orte/mca/sstore/sstore.h"
> >
> > mca/mpool/sm/mpool_sm_module.c
> > 34:#include "orte/mca/sstore/sstore.h"
> > -
> >
> > --
> > Jeff Squyres
> > jsquy...@cisco.com
> > For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
> >
> > ___
> > devel mailing list
> > de...@open-mpi.org
> > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> > Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/08/15570.php
> >
> > ___
> > devel mailing list
> > de...@open-mpi.org
> > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> > Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/08/15571.php
>
>
> --
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
>
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/08/15587.php
>



-- 
Joshua Hursey
Assistant Professor of Computer Science
University of Wisconsin-La Crosse
http://cs.uwlax.edu/~jjhursey

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, 2014 at 4:36 PM, Jeff Squyres (jsquyres)  
> wrote:
> Here's a few ORTE headers in OPAL source -- can respective owners clean these 
> up?  Thanks.
> 
> -
> mca/btl/smcuda/btl_smcuda.c
> 63:#include "orte/mca/sstore/sstore.h"
> 
> mca/btl/sm/btl_sm.c
> 62:#include "orte/mca/sstore/sstore.h"
> 
> mca/mpool/sm/mpool_sm_module.c
> 34:#include "orte/mca/sstore/sstore.h"
> -
> 
> --
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to: 
> http://www.cisco.com/web/about/doing_business/legal/cri/
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/08/15570.php
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/08/15571.php


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

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 list the four instances I encountered while building the 
> C++ bindings, but there might be others.
> 
> -Paul
> 
> "openmpi-1.8.2rc4r32480/ompi/include/ompi/constants.h", line 70: Warning: 
> Identifier expected instead of "}".
> "openmpi-1.8.2rc4r32480/opal/mca/base/mca_base_framework.h", line 37: 
> Warning: Identifier expected instead of "}".
> "openmpi-1.8.2rc4r32480/opal/mca/base/mca_base_framework.h", line 119: 
> Warning: Identifier expected instead of "}".
> "openmpi-1.8.2rc4r32480/opal/mca/base/mca_base_var.h", line 694: Warning: 
> Identifier expected instead of "}".
> 
> 
> -- 
> 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-510-486-6900
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/08/15576.php


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

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

2014-08-09 Thread Mike Dubman

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_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: 'ORTE_PROC_FLAG_WAITPID'
> undeclared (first use in this function)
> >
> > 02:36:30
> > base/odls_base_default_fns.c:2001: error: (Each undeclared identifier is
> reported only once
> >
> > 02:36:30
> > base/odls_base_default_fns.c:2001: error: for each function it appears
> in.)
> >
> > 02:36:30
> > base/odls_base_default_fns.c:2004: warning: implicit declaration of
> function 'ORTE_FLAG_TEST'
> >
> > 02:36:30
> > base/odls_base_default_fns.c:2004: error: 'ORTE_PROC_FLAG_IOF_COMPLETE'
> undeclared (first use in this function)
> >
> > 02:36:30
> > base/odls_base_default_fns.c:2005: warning: implicit declaration of
> function 'ORTE_FLAG_UNSET'
> >
> > 02:36:30
> > base/odls_base_default_fns.c:2005: error: 'ORTE_PROC_FLAG_ALIVE'
> undeclared (first use in this function)
> >
> > 02:36:30
> > make[2]: *** [base/odls_base_default_fns.lo] Error 1
> >
> > 02:36:30
> > make[2]: Leaving directory
> `/scrap/jenkins/scrap/workspace/hpc-ompi-shmem/label/hpc-test-node/orte/mca/odls'
> >
> > 02:36:30
> > make[1]: *** [install-recursive] Error 1
> >
> > 02:36:30
> > make[1]: Leaving directory
> `/scrap/jenkins/scrap/workspace/hpc-ompi-shmem/label/hpc-test-node/orte'
> >
> > 02:36:30
> > make: *** [install-recursive] Error 1
> >
> > 02:36:30
> > Build step 'Execute shell' marked build as failure
> >
> >
> > ___
> > devel mailing list
> > de...@open-mpi.org
> > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> > Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/08/15580.php
>
>
> --
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
>
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/08/15584.php
>

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: warning: implicit declaration of function 
> 'ORTE_FLAG_SET'
> 
> 02:36:30 
> base/odls_base_default_fns.c:2001: error: 'ORTE_PROC_FLAG_WAITPID' undeclared 
> (first use in this function)
> 
> 02:36:30 
> base/odls_base_default_fns.c:2001: error: (Each undeclared identifier is 
> reported only once
> 
> 02:36:30 
> base/odls_base_default_fns.c:2001: error: for each function it appears in.)
> 
> 02:36:30 
> base/odls_base_default_fns.c:2004: warning: implicit declaration of function 
> 'ORTE_FLAG_TEST'
> 
> 02:36:30 
> base/odls_base_default_fns.c:2004: error: 'ORTE_PROC_FLAG_IOF_COMPLETE' 
> undeclared (first use in this function)
> 
> 02:36:30 
> base/odls_base_default_fns.c:2005: warning: implicit declaration of function 
> 'ORTE_FLAG_UNSET'
> 
> 02:36:30 
> base/odls_base_default_fns.c:2005: error: 'ORTE_PROC_FLAG_ALIVE' undeclared 
> (first use in this function)
> 
> 02:36:30 
> make[2]: *** [base/odls_base_default_fns.lo] Error 1
> 
> 02:36:30 
> make[2]: Leaving directory 
> `/scrap/jenkins/scrap/workspace/hpc-ompi-shmem/label/hpc-test-node/orte/mca/odls'
> 
> 02:36:30 
> make[1]: *** [install-recursive] Error 1
> 
> 02:36:30 
> make[1]: Leaving directory 
> `/scrap/jenkins/scrap/workspace/hpc-ompi-shmem/label/hpc-test-node/orte'
> 
> 02:36:30 
> make: *** [install-recursive] Error 1
> 
> 02:36:30 
> Build step 'Execute shell' marked build as failure
> 
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/08/15580.php


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

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/ticket/4826
> 
> I've been able to confirm that the nightly tarball (1.8.2rc4r32480) works as 
> expected on the SPARC and PPC64 platforms where I had reproduced the problem 
> previously.  I won't have access to the IA64 platform (which also has 
> pagesize != 4K) until about 6 hours from now, but have no doubt the fix will 
> work there too.
> 
> -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-510-486-6900
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/08/15574.php


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

[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):

"/shared/OMPI/openmpi-1.8-latest-solaris11-x86-ib-ss12u3/openmpi-1.8.2rc4r32480/ompi/mpi/cxx/file.cc",
Error: The function opal_atomic_add_32(volatile int*, int) has not had a
body defined.

Brian attached a possible fix to
http://www.open-mpi.org/community/lists/users/2013/01/21272.php
It applies cleanly to v1.8 but appears to make things worse, trading that
one error for two:

"/shared/OMPI/openmpi-1.8-latest-solaris11-x86-ib-ss12u3/openmpi-1.8.2rc4r32480/opal/include/opal/sys/atomic_impl.h",
line 106: Error: opal_atomic_add_64(volatile long long*, long long) was
previously declared "extern", not "inline".
"/shared/OMPI/openmpi-1.8-latest-solaris11-x86-ib-ss12u3/openmpi-1.8.2rc4r32480/opal/include/opal/sys/atomic_impl.h",
line 121: Error: opal_atomic_sub_64(volatile long long*, long long) was
previously declared "extern", not "inline".


The good news is that the problem does not exist on the trunk.
So, hopefully somebody can track down the proper changes to CMR.

-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-510-486-6900

Re: [OMPI devel] jenkins error in trunk

2014-08-09 Thread Mike Dubman

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: assignment discards qualifiers
from pointer target type*04:58:49* make[2]: ***
[coll_fca_component.lo] Error 1*04:58:49* make[2]: Leaving directory
`/scrap/jenkins/scrap/workspace/hpc-ompi-shmem-3/label/hpc-test-node/ompi/mca/coll/fca'



On Fri, Aug 8, 2014 at 7:12 PM, Ralph Castain  wrote:

> Fixed in r32462
>
> On Aug 8, 2014, at 8:13 AM, Mike Dubman  wrote:
>
>
> *Josh,Devendar - could you please take a look?*
>
> *Thanks*
>
>
> *15:45:00* Making install in mca/coll/fca*15:45:00* make[2]: Entering 
> directory 
> `/scrap/jenkins/scrap/workspace/hpc-ompi-shmem/label/hpc-test-node/ompi/mca/coll/fca'*15:45:00*
>CC   coll_fca_module.lo*15:45:00* coll_fca_module.c: In function 
> 'have_remote_peers':*15:45:00* coll_fca_module.c:48: error: 'ompi_proc_t' has 
> no member named 'proc_flags'*15:45:00* coll_fca_module.c:48: error: 
> 'ompi_proc_t' has no member named 'proc_flags'*15:45:00* coll_fca_module.c: 
> In function '__get_local_ranks':*15:45:00* coll_fca_module.c:75: error: 
> 'ompi_proc_t' has no member named 'proc_flags'*15:45:00* 
> coll_fca_module.c:75: error: 'ompi_proc_t' has no member named 
> 'proc_flags'*15:45:00* coll_fca_module.c:95: error: 'ompi_proc_t' has no 
> member named 'proc_flags'*15:45:00* coll_fca_module.c:95: error: 
> 'ompi_proc_t' has no member named 'proc_flags'*15:45:00* make[2]: *** 
> [coll_fca_module.lo] Error 1*15:45:00* make[2]: Leaving directory 
> `/scrap/jenkins/scrap/workspace/hpc-ompi-shmem/label/hpc-test-node/ompi/mca/coll/fca'*15:45:00*
>  make[1]: *** [install-recursive] Error 1*15:45:00* make[1]: Leaving 
> directory 
> `/scrap/jenkins/scrap/workspace/hpc-ompi-shmem/label/hpc-test-node/ompi'*15:45:00*
>  make: *** [install-recursive] Error 1*15:45:00* Build step 'Execute shell' 
> marked build as failu
>
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/08/15557.php
>
>
>
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/08/15558.php
>

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'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-x86_64-java/BLD/ompi/mpi/java/java'
>   JAVAC  MPI.class
> /usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:92:
> type parameters of T cannot be determined; no unique maximal instance
> exists for type variable T with upper bounds T,mpi.Struct.Data
> return newData(buffer, 0);
>   ^
> /usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:107:
> type parameters of T cannot be determined; no unique maximal instance
> exists for type variable T with upper bounds T,mpi.Struct.Data
> return newData(buffer, index * extent);
>   ^
> /usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:120:
> type parameters of T cannot be determined; no unique maximal instance
> exists for type variable T with upper bounds T,mpi.Struct.Data
> return getData(buffer);
>   ^
> /usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:136:
> type parameters of T cannot be determined; no unique maximal instance
> exists for type variable T with upper bounds T,mpi.Struct.Data
> return getData(buffer, index);
>   ^
> /usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:722:
> type parameters of T cannot be determined; no unique maximal instance
> exists for type variable T with upper bounds D,mpi.Struct.Data
> return s.newData(buffer, offset + field);
> ^
> /usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:737:
> type parameters of T cannot be determined; no unique maximal instance
> exists for type variable T with upper bounds D,mpi.Struct.Data
> return s.newData(buffer, offset + field + index * s.extent);
> ^
> 6 errors
>
>
>
> --
> 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-510-486-6900
>  ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/08/15575.php
>
>
>
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/08/15577.php
>



-- 
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-510-486-6900

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 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-x86_64-java/BLD/ompi/mpi/java/java'
>   JAVAC  MPI.class
> /usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:92:
>  type parameters of T cannot be determined; no unique maximal instance 
> exists for type variable T with upper bounds T,mpi.Struct.Data
> return newData(buffer, 0);
>   ^
> /usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:107:
>  type parameters of T cannot be determined; no unique maximal instance 
> exists for type variable T with upper bounds T,mpi.Struct.Data
> return newData(buffer, index * extent);
>   ^
> /usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:120:
>  type parameters of T cannot be determined; no unique maximal instance 
> exists for type variable T with upper bounds T,mpi.Struct.Data
> return getData(buffer);
>   ^
> /usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:136:
>  type parameters of T cannot be determined; no unique maximal instance 
> exists for type variable T with upper bounds T,mpi.Struct.Data
> return getData(buffer, index);
>   ^
> /usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:722:
>  type parameters of T cannot be determined; no unique maximal instance 
> exists for type variable T with upper bounds D,mpi.Struct.Data
> return s.newData(buffer, offset + field);
> ^
> /usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:737:
>  type parameters of T cannot be determined; no unique maximal instance 
> exists for type variable T with upper bounds D,mpi.Struct.Data
> return s.newData(buffer, offset + field + index * s.extent);
> ^
> 6 errors
> 
> 
> 
> -- 
> 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-510-486-6900
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/08/15575.php

[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-1.8.2rc4r32480/ompi/include/ompi/constants.h", line 70: Warning:
Identifier expected instead of "}".
"openmpi-1.8.2rc4r32480/opal/mca/base/mca_base_framework.h", line 37:
Warning: Identifier expected instead of "}".
"openmpi-1.8.2rc4r32480/opal/mca/base/mca_base_framework.h", line 119:
Warning: Identifier expected instead of "}".
"openmpi-1.8.2rc4r32480/opal/mca/base/mca_base_var.h", line 694: Warning:
Identifier expected instead of "}".


-- 
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-510-486-6900

[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-x86_64-java/BLD/ompi/mpi/java/java'
  JAVAC  MPI.class
/usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:92:
type parameters of T cannot be determined; no unique maximal instance
exists for type variable T with upper bounds T,mpi.Struct.Data
return newData(buffer, 0);
  ^
/usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:107:
type parameters of T cannot be determined; no unique maximal instance
exists for type variable T with upper bounds T,mpi.Struct.Data
return newData(buffer, index * extent);
  ^
/usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:120:
type parameters of T cannot be determined; no unique maximal instance
exists for type variable T with upper bounds T,mpi.Struct.Data
return getData(buffer);
  ^
/usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:136:
type parameters of T cannot be determined; no unique maximal instance
exists for type variable T with upper bounds T,mpi.Struct.Data
return getData(buffer, index);
  ^
/usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:722:
type parameters of T cannot be determined; no unique maximal instance
exists for type variable T with upper bounds D,mpi.Struct.Data
return s.newData(buffer, offset + field);
^
/usr/users/6/hargrove/SCRATCH/OMPI/openmpi-1.8-latest-linux-x86_64-java/openmpi-1.8.2rc4r32480/ompi/mpi/java/java/Struct.java:737:
type parameters of T cannot be determined; no unique maximal instance
exists for type variable T with upper bounds D,mpi.Struct.Data
return s.newData(buffer, offset + field + index * s.extent);
^
6 errors



-- 
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-510-486-6900

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

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/ticket/4826
>

I've been able to confirm that the nightly tarball (1.8.2rc4r32480) works
as expected on the SPARC and PPC64 platforms where I had reproduced the
problem previously.  I won't have access to the IA64 platform (which also
has pagesize != 4K) until about 6 hours from now, but have no doubt the fix
will work there too.

-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-510-486-6900

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