X-Git-Url: http://git.madism.org/?p=apps%2Fmadmutt.git;a=blobdiff_plain;f=mutt_sasl.c;h=6b6f0ea4674617b135a78f12e1850e23547e2bab;hp=c93413db2cb9d0d4cbe6f6eb89410afedf27d38e;hb=4eaac5c4a87b84ea9ec0668b4e088ac27e2d1106;hpb=b85f52d2ec4d820ab5c4b577857548bec294bb27

diff --git a/mutt_sasl.c b/mutt_sasl.c
index c93413d..6b6f0ea 100644
--- a/mutt_sasl.c
+++ b/mutt_sasl.c
@@ -69,7 +69,6 @@ static int getnameinfo_err (int ret)
   }
   return err;
 }
-#endif
 
 /* arbitrary. SASL will probably use a smaller buffer anyway. OTOH it's
  * been a while since I've had access to an SASL server which negotiated
@@ -123,7 +122,6 @@ static int iptostring (const struct sockaddr *addr, socklen_t addrlen,
 
   return SASL_OK;
 }
-#endif
 
 /* mutt_sasl_start: called before doing a SASL exchange - initialises library
  *   (if necessary). */
@@ -364,12 +362,12 @@ void mutt_sasl_setup_conn (CONNECTION * conn, sasl_conn_t * saslconn)
 
   sasldata->saslconn = saslconn;
   /* get ssf so we know whether we have to (en|de)code read/write */
-  sasl_getprop (saslconn, SASL_SSF, (const void **) &sasldata->ssf);
+  sasl_getprop (saslconn, SASL_SSF, (const void **)(void *)&sasldata->ssf);
   debug_print (3, ("SASL protection strength: %u\n", *sasldata->ssf));
   /* Add SASL SSF to transport SSF */
   conn->ssf += *sasldata->ssf;
   sasl_getprop (saslconn, SASL_MAXOUTBUF,
-                (const void **) &sasldata->pbufsize);
+                (const void **)(void *)&sasldata->pbufsize);
   debug_print (3, ("SASL protection buffer size: %u\n", *sasldata->pbufsize));
 
   /* clear input buffer */