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

Jonathan G. Atencio jatencio at gmail.com
Thu Jun 4 16:35:55 EDT 2009


Hello Jonathan,

This "fix" worked for me.

Thanks,

Jonathan

On Thu, Jun 4, 2009 at 1:49 PM, Jonathan Perkins
<perkinjo at cse.ohio-state.edu> wrote:
> On Thu, Jun 04, 2009 at 02:12:46PM -0400, Jonathan Perkins wrote:
>> On Thu, Jun 04, 2009 at 11:36:48AM -0600, Jonathan G. Atencio wrote:
>> > I am running RHEl4 with Infiniband. I see similar errors as well.
>>
>> This may be a rhel4 specific issue.  Can Nathan and Le provide details
>> of their OS as well as cpu architecture?
>
> We've reproduced the error on rhel4 machine and found a couple
> resolutions.  Let me suggest that users on rhel4 add '-D_GNU_SOURCE' to
> their CFLAGS until we provide a new version that takes care of this
> internally.
>
> The following should work...
> % ./configure CFLAGS='-D_GNU_SOURCE'
> % make
>
>>
>> >
>> > If I pass "-D_XOPEN_SOURCE=600" to my CFLAGS, then run configure, I am
>> > able to get past the original error, however, I encounter another
>> > error:
>> >
>> > % export CFLAGS="-D_XOPEN_SOURCE=600"
>> > % ./configure
>> > ...
>> > % make
>> > ...
>> > gcc -DHAVE_CONFIG_H -I. -I.
>> > -I/home/atencio/mvapich2-1.4rc1/src/pm/mpirun/include
>> > -D_XOPEN_SOURCE=600 -DNDEBUG -O2
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/ch3/include
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/ch3/include
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/common/datatype
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/common/datatype
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/common/locks
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/common/locks
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/ch3/channels/mrail/include
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/ch3/channels/mrail/include
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/ch3/channels/mrail/src/gen2
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/ch3/channels/mrail/src/gen2
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/common/locks
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/common/locks
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/ch3/include
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/ch3/include
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/common/datatype
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/common/datatype
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/common/locks
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/common/locks
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/ch3/channels/mrail/include
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/ch3/channels/mrail/include
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/ch3/channels/mrail/src/gen2
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/ch3/channels/mrail/src/gen2
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/common/locks
>> > -I/home/atencio/mvapich2-1.4rc1/src/mpid/common/locks -c
>> > mpispawn_tree.c
>> > mpispawn_tree.c: In function `mpispawn_tree_init':
>> > mpispawn_tree.c:176: error: `fd_set' undeclared (first use in this function)
>> > mpispawn_tree.c:176: error: (Each undeclared identifier is reported only once
>> > mpispawn_tree.c:176: error: for each function it appears in.)
>> > mpispawn_tree.c:176: error: syntax error before "set"
>> > mpispawn_tree.c:177: error: storage size of 'tv' isn't known
>> > mpispawn_tree.c:191: error: `set' undeclared (first use in this function)
>> > make[3]: *** [mpispawn_tree.o] Error 1
>> > make[3]: Leaving directory `/mscf/home/atencio/mvapich2-1.4rc1/src/pm/mpirun'
>> > make[2]: *** [all-redirect] Error 2
>> > make[2]: Leaving directory `/mscf/home/atencio/mvapich2-1.4rc1/src/pm'
>> > make[1]: *** [all-redirect] Error 2
>> > make[1]: Leaving directory `/mscf/home/atencio/mvapich2-1.4rc1/src'
>> > make: *** [all-redirect] Error 2
>> >
>> >
>> > Regards,
>> >
>> > Jonathan
>> >
>> > On Thu, Jun 4, 2009 at 10:34 AM, Le Yan <lyan1 at cct.lsu.edu> 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
>> > >
>> >
>> > _______________________________________________
>> > mvapich-discuss mailing list
>> > mvapich-discuss at cse.ohio-state.edu
>> > http://mail.cse.ohio-state.edu/mailman/listinfo/mvapich-discuss
>>
>> --
>> Jonathan Perkins
>> http://www.cse.ohio-state.edu/~perkinjo
>
>
>
> --
> Jonathan Perkins
> http://www.cse.ohio-state.edu/~perkinjo
>



More information about the mvapich-discuss mailing list