[mvapich-discuss] mvapich2-1.2 compilation error for debug options

[Ajay Sampat]

Hello Nilesh Awate/ Gossips J,

We now have a fix for the compilation problems you reported while
using mem tracing debug options.

You can find this fix on the latest nightly tarball from April 25th
onwards here.
http://mvapich.cse.ohio-state.edu/nightly/mvapich2/branches/1.2/

You can also signup to our mvapich-commit mailing list and keep
up with all the commits to MVAPICH2 bug fix branches here.
http://mail.cse.ohio-state.edu/mailman/listinfo/mvapich-commit/

This fix will also be available in the upcoming MVAPICH2 release.

Thanks.

On Fri, Apr 17, 2009 at 10:06 AM, Dhabaleswar Panda
<panda at cse.ohio-state.edu> wrote:
> Thanks for your notes. We plan to resolve this issue in the upcoming
> release (in a few weeks).
>
> Thanks,
>
> DK
>
> On Fri, 17 Apr 2009, gossips J wrote:
>
>> Yes, same observation for me too.
>>
>> It looks like there is a bug in mvapich2 compilation process with “—enable-g
>> –enable-debuginfo” option.
>>
>> It never compiles debug library for mavpich2.
>>
>> It contains primitive calls for memory allocation at some places which it
>> doesn’t allow to compile during debug configured mvapich2.
>>
>> Let us hope that it will resolve in next release.
>>
>> Thanks,
>>
>> Polk.
>>
>> On Fri, Apr 17, 2009 at 1:04 PM, nilesh awate <nilesh_awate at yahoo.com>wrote:
>>
>> >
>> > Hi all,
>> >
>> > I am using mvapich2-q.2p1 over gen2
>> >
>> > for debugging purpose i  wanted to use --enable-g=mem option
>> >
>> > configurations options are
>> >
>> > ./configure  --enable-g=mem --prefix=/home/anuj/mvapich2_1_2/
>> > --with-rdma=gen2 --with-ib-include=/usr/local/ofed/include/
>> > --with-ib-libpath=/usr/local/ofed/lib64/ --enable-sharedlibs=gcc
>> > --enable-debuginfo
>> >
>> >
>> > but it started giving me following error over both the adi
>> >
>> > ch3_smp_progress.c:815:58: warning: character constant too long for its
>> > type
>> > ch3_smp_progress.c: In function `MPIDI_CH3I_SMP_init':
>> > ch3_smp_progress.c:815: error: syntax error before ':' token
>> > ch3_smp_progress.c:828:59: warning: character constant too long for its
>> > type
>> > ch3_smp_progress.c:828: error: syntax error before ':' token
>> > make[7]: Leaving directory
>> > `/tmp/mvapich2-1.2p1/src/mpid/ch3/channels/mrail/src/rdma'
>> >
>> > I brows above error code which is under  #if !defined(_X86_64_)
>> >
>> > so i just defined that flag to omit that part of the code but for next
>> > compilation it flush same error for
>> >
>> > other part of the code
>> >
>> > ch3u_rma_sync.c:205:74: warning: character constant too long for its type
>> > ch3u_rma_sync.c: In function `MPIDI_Win_fence':
>> > ch3u_rma_sync.c:205: error: syntax error before ':' token
>> > ch3u_rma_sync.c:233:27: warning: character constant too long for its type
>> > ch3u_rma_sync.c:233: error: syntax error before ':' token
>> >
>> > What should i do to have mvapich libraries with debugging
>> > options(spacifically memory tracing)
>> >
>> > waiting for reply
>> > Nilesh Awate
>> >
>> >
>> >
>> >
>> >
>> > ------------------------------
>> > Add more friends to your messenger and enjoy! Invite them now.<http://in.rd.yahoo.com/tagline_messenger_6/*http://messenger.yahoo.com/invite/>
>> >
>> > _______________________________________________
>> > 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
>



-- 
Ajay Sampat