[mvapich-discuss] Build error with mvapich2-1.4-RC1-3378

[Dhabaleswar Panda]

We are taking a look at these issues and will get back to you soon.

DK

On Thu, 4 Jun 2009, Le Yan wrote:

> Hi there,
>
> I have exactly the same error with GNU and Intel compilers, at the very
> beginning though. The building options are the same, except the "slurm"
> part.
>
> Cheers,
> Le
>
> On Wed, 2009-06-03 at 13:43 -0600, Nathan Baca wrote:
> > Hello,
> >
> > I am trying to build the new release candidate and am getting a
> > consistent build error. It seems to happen at the very end of the
> > build and has failed with: gcc3.4, gcc4.1, intel10.1.015, and
> > pathscale3.2. The same build process successfully builds
> > mvapich2-1.2p1. Anybody else seen this?
> >
> > My configure line and error is as follows:
> >
> > ./configure --prefix=1.4rc1-pathscale-3.2 --with-slurm=/opt/hptc/slurm
> > --enable-romio --with-file-system=lustre CC=pathcc CXX=pathCC
> > F77=pathf90 FC=pathf90
> >
> > make[5]: Entering directory
> > `/ram/tmp/mvapich2-build/mvapich2-1.4rc1/src/mpid/common/locks'
> > pathcc -DHAVE_CONFIG_H -I. -I. -I. -I../../../include
> > -I/tmp/mvapich2-build/mvapich2-1.4rc1/src/include -DNDEBUG -O2
> > -I/tmp/mvapich2-build/mvapich2-1.4rc1/src/mpid/ch3/include
> > -I/tmp/mvapich2-build/mvapich2-1.4rc1/src/mpid/ch3/include
> > -I/tmp/mvapich2-build/mvapich2-1.4rc1/src/mpid/common/datatype
> > -I/tmp/mvapich2-build/mvapich2-1.4rc1/src/mpid/common/datatype
> > -I/tmp/mvapich2-build/mvapich2-1.4rc1/src/mpid/common/locks
> > -I/tmp/mvapich2-build/mvapich2-1.4rc1/src/mpid/common/locks
> > -I/tmp/mvapich2-build/mvapich2-1.4rc1/src/mpid/ch3/channels/mrail/include -I/tmp/mvapich2-build/mvapich2-1.4rc1/src/mpid/ch3/channels/mrail/include -I/tmp/mvapich2-build/mvapich2-1.4rc1/src/mpid/ch3/channels/mrail/src/gen2 -I/tmp/mvapich2-build/mvapich2-1.4rc1/src/mpid/ch3/channels/mrail/src/gen2 -I/tmp/mvapich2-build/mvapich2-1.4rc1/src/mpid/common/locks -I/tmp/mvapich2-build/mvapich2-1.4rc1/src/mpid/common/locks -c mpidu_process_locks.c
> > In file included
> > from /tmp/mvapich2-build/mvapich2-1.4rc1/src/mpid/ch3/channels/mrail/src/gen2/ibv_param.h:18,
> >
> > from /tmp/mvapich2-build/mvapich2-1.4rc1/src/mpid/ch3/channels/mrail/src/gen2/vbuf.h:32,
> >
> > from /tmp/mvapich2-build/mvapich2-1.4rc1/src/mpid/ch3/channels/mrail/src/gen2/mpidi_ch3_rdma_pre.h:23,
> >
> > from /tmp/mvapich2-build/mvapich2-1.4rc1/src/mpid/ch3/channels/mrail/include/mpidi_ch3_pre.h:23,
> >
> > from /tmp/mvapich2-build/mvapich2-1.4rc1/src/mpid/ch3/include/mpidpre.h:43,
> >                  from ../../../include/mpiimpl.h:115,
> >
> > from /tmp/mvapich2-build/mvapich2-1.4rc1/src/mpid/ch3/include/mpidimpl.h:36,
> >                  from mpidu_process_locks.h:32,
> >                  from mpidu_process_locks.c:6:
> > /tmp/mvapich2-build/mvapich2-1.4rc1/src/mpid/ch3/channels/mrail/src/gen2/../rdma/coll_shmem.h:100: error: syntax error before "pthread_spinlock_t"
> >
> >
> > --
> > Nathan Baca
> > nathan.baca at gmail.com
> > _______________________________________________
> > mvapich-discuss mailing list
> > mvapich-discuss at cse.ohio-state.edu
> > http://mail.cse.ohio-state.edu/mailman/listinfo/mvapich-discuss
>
> _______________________________________________
> mvapich-discuss mailing list
> mvapich-discuss at cse.ohio-state.edu
> http://mail.cse.ohio-state.edu/mailman/listinfo/mvapich-discuss
>