tcpdump mailing list archives

HP-UX 11.11 compiltion of tcpdump-2004-09-15


From: Rick Jones <rick.jones2 () hp com>
Date: Wed, 15 Sep 2004 10:50:20 -0700

The latest (2004-09-15) tcpdump bits appear to compile cleanly as 32-bit on HP-UX 11.11 (11i v1) with the HP compiler, and then links with the 2004-09-13 libpcap.

There are two warnings in the output of the compiler:

cc -O -DHAVE_CONFIG_H -I./../libpcap -I/usr/local/include -I/usr//include -I./missing -D_U_="" -I. -I./../libpcap -I/usr/local/include -I/usr//include -I./missing -c ./print-esp.c cc: "print-esp.c", line 476: warning 604: Pointers are not assignment-compatible. cc: "print-esp.c", line 476: warning 563: Argument #3 is not the correct type.


and then later

cc -O -DHAVE_CONFIG_H  -I./../libpcap  -I/usr/local/include -I/usr//incl
ude -I./missing -D_U_="" -I. -I./../libpcap -I/usr/local/include -I/usr//include -I./missing -c ./print-tcp.c cc: "print-tcp.c", line 800: warning 604: Pointers are not assignment-compatible. cc: "print-tcp.c", line 800: warning 563: Argument #1 is not the correct type.


The former seems to be this call:

                if (EVP_CipherInit(&ctx, sa->evp, secret, NULL, 0) < 0)
                        (*ndo->ndo_warning)(ndo, "espkey init failed");

where "secret" is a char *, but the manpage for EVP_CipherInit (OpenSSL that came along in the HP Internet Express bundle from www.software.hp.com) seems to want an "unsigned char *" instead :)

The warning in print-tcp.c seems to be for:

        MD5_Final(sig, &ctx);

where "sig" is "char sig[TCP_SIGLEN]" but MD5_Final seems to want an "unsigned char *"


In other words, variations on the familiar char versus unsigned char theme :)

A quick "./tcpdump -c 10" on the compilation system appears to have been happy.

rick jones
-
This is the tcpdump-workers list.
Visit https://lists.sandelman.ca/ to unsubscribe.


Current thread: