There is little interest in supporting Watt-32 TCP/IP debugging. For

reference, check out http://www.watt-32.net/
ok jsing

1 files changed, 0 insertions, 7 deletions

diff --git a/src/lib/libssl/src/apps/s_client.c b/src/lib/libssl/src/apps/s_client.c
index 528864d265..66feb0d66b 100644
--- a/src/lib/libssl/src/apps/s_client.c
+++ b/src/lib/libssl/src/apps/s_client.c
@@ -287,9 +287,6 @@ sc_usage(void)
         BIO_printf(bio_err, " -pause        - sleep(1) after each read(2) and write(2) system call\n");
         BIO_printf(bio_err, " -showcerts    - show all certificates in the chain\n");
         BIO_printf(bio_err, " -debug        - extra output\n");
-#ifdef WATT32
-        BIO_printf(bio_err, " -wdebug       - WATT-32 tcp debugging\n");
-#endif
         BIO_printf(bio_err, " -msg          - Show protocol messages\n");
         BIO_printf(bio_err, " -nbio_test    - more ssl protocol testing\n");
         BIO_printf(bio_err, " -state        - print the 'ssl' states\n");
@@ -554,10 +551,6 @@ s_client_main(int argc, char **argv)
                 else if (strcmp(*argv, "-status") == 0)
                         c_status_req = 1;
 #endif
-#ifdef WATT32
-                else if (strcmp(*argv, "-wdebug") == 0)
-                        dbug_init();
-#endif
                 else if (strcmp(*argv, "-msg") == 0)
                         c_msg = 1;
                 else if (strcmp(*argv, "-showcerts") == 0)