[mvapich-discuss] viainit.c errors in mvapich-0.9.7 build/topspin

[Sayantan Sur]

Hello Steve,

* On Apr,2 Steve Jones<stevejones at stanford.edu> wrote :
> hi.
> 
> i realized this is a similar issue faced in 0.9.6-122. below is the patch
> for the previous version that was sent from nbcl. it's my guess this same
> fix should resolve it, correct?

Thanks for reporting this to the list. Yes, I believe the patch we sent
you earlier for 0.9.6-122 should resolve the issue. I am attaching a
similar patch for 0.9.7 with this email which should apply cleanly to
0.9.7. Please use this one instead. As usual, the process to apply the
patch is:

$ patch -p1 < vapi_ver_code_patch

If you could report back to the list, whether this worked or not, it'll
be great!

Thanks,
Sayantan.

-- 
http://www.cse.ohio-state.edu/~surs
-------------- next part --------------
diff -Naur mvapich-0.9.7/mpid/vapi/viainit.c mvapich-0.9.7-patched/mpid/vapi/viainit.c
--- mvapich-0.9.7/mpid/vapi/viainit.c	2006-03-12 17:26:08.000000000 -0500
+++ mvapich-0.9.7-patched/mpid/vapi/viainit.c	2006-04-17 10:50:25.000000000 -0400
@@ -166,6 +166,7 @@
     case VAPI_SEND_QUEUE_DRAINED:
     case VAPI_PORT_ACTIVE:
 #ifdef VAPI_VERSION_CODE
+#if 0
 #if VAPI_VERSION_CODE >= VAPI_VERSION(4,1,0)
     case VAPI_CLIENT_REREGISTER:
     case VAPI_RECEIVE_QUEUE_DRAINED:
@@ -173,6 +174,7 @@
     case VAPI_PATH_MIG_ARMED:
 #endif
 #endif
+#endif
         {
             D_PRINT("Got an asynchronous event: %s\n",
                     VAPI_event_record_sym(event_p->type));
@@ -187,10 +189,12 @@
     case VAPI_LOCAL_CATASTROPHIC_ERROR:
     case VAPI_PORT_ERROR:
 #ifdef VAPI_VERSION_CODE
+#if 0
 #if VAPI_VERSION_CODE >= VAPI_VERSION(4,1,0)
     case VAPI_SRQ_CATASTROPHIC_ERROR:
 #endif
 #endif
+#endif
         {
             vapidev_error_abort(GEN_EXIT_ERR,
                                 "Got an asynchronous event: %s (%s)",