Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

Subject: Re: [OMPI devel] 1.7.4rc: build failure on mips32 and ppc32
From: Paul Hargrove (phhargrove_at_[hidden])
Date: 2014-01-17 23:40:42


Well, the good news is that the trunk builds fine on ppc32.
So, I suspect there is a fix that needs a CMR.
I'll poke around a bit, to see if I can locate the necessary changes.

My mips32 system is slow, but I am hoping for similar results on trunk.

-Paul

On Fri, Jan 17, 2014 at 7:49 PM, Paul Hargrove <phhargrove_at_[hidden]> wrote:

> Yup, gcc on ppc32 (one nightly later, btw) fails just as mips32 did:
>
> make[2]: Entering directory
> `/home/phargrov/OMPI/openmpi-1.7.4-latest-linux-ppc32/BLD/ompi/mpi/cxx'
> CXX mpicxx.lo
> In file included from
> /home/phargrov/OMPI/openmpi-1.7.4-latest-linux-ppc32/openmpi-1.7.4rc2r30318/opal/class/opal_pointer_array.h:37,
> from
> /home/phargrov/OMPI/openmpi-1.7.4-latest-linux-ppc32/openmpi-1.7.4rc2r30318/ompi/errhandler/errhandler.h:32,
> from
> /home/phargrov/OMPI/openmpi-1.7.4-latest-linux-ppc32/openmpi-1.7.4rc2r30318/ompi/mpi/cxx/mpicxx.cc:37:
> /home/phargrov/OMPI/openmpi-1.7.4-latest-linux-ppc32/openmpi-1.7.4rc2r30318/opal/threads/mutex.h:
> In function 'int64_t OPAL_THREAD_ADD64(volatile int64_t*, int)':
> /home/phargrov/OMPI/openmpi-1.7.4-latest-linux-ppc32/openmpi-1.7.4rc2r30318/opal/threads/mutex.h:292:
> error: 'opal_atomic_add_64' was not declared in this scope
> make[2]: *** [mpicxx.lo] Error 1
>
>
> -Paul
>
>
> On Fri, Jan 17, 2014 at 7:00 PM, Paul Hargrove <phhargrove_at_[hidden]> wrote:
>
>> Trying to build 1.7.4rc2r30303 with gcc on linux/mips32 yields the
>> following failure:
>>
>> CXX mpicxx.lo
>> /home/phargrov/OMPI/openmpi-1.7.4-latest-linux-mips32/openmpi-1.7.4rc2r30303/ompi/mpi/cxx/mpicxx.cc:31:2:
>> warning: #ident is a deprecated GCC extension
>> In file included from
>> /home/phargrov/OMPI/openmpi-1.7.4-latest-linux-mips32/openmpi-1.7.4rc2r30303/opal/class/opal_pointer_array.h:37,
>> from
>> /home/phargrov/OMPI/openmpi-1.7.4-latest-linux-mips32/openmpi-1.7.4rc2r30303/ompi/errhandler/errhandler.h:32,
>> from
>> /home/phargrov/OMPI/openmpi-1.7.4-latest-linux-mips32/openmpi-1.7.4rc2r30303/ompi/mpi/cxx/mpicxx.cc:37:
>> /home/phargrov/OMPI/openmpi-1.7.4-latest-linux-mips32/openmpi-1.7.4rc2r30303/opal/threads/mutex.h:
>> In function 'int64_t OPAL_THREAD_ADD64(volatile int64_t*, int)':
>> /home/phargrov/OMPI/openmpi-1.7.4-latest-linux-mips32/openmpi-1.7.4rc2r30303/opal/threads/mutex.h:292:
>> error: 'opal_atomic_add_64' was not declared in this scope
>>
>> This looks VERY similar to the problem I reported recently w/ xlc on
>> ppc32 ( http://www.open-mpi.org/community/lists/devel/2014/01/13801.php )
>> I am checking gcc on ppc32 now...
>>
>> -Paul
>>
>> --
>> Paul H. Hargrove PHHargrove_at_[hidden]
>> 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 PHHargrove_at_[hidden]
> 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                          PHHargrove_at_[hidden]
Future Technologies Group
Computer and Data Sciences Department     Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory     Fax: +1-510-486-6900