You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Sanjay Cherubala <sp...@koame001.delcoelect.com> on 1999/05/17 15:29:23 UTC
os-hpux/4428: Warning message during compile
>Number: 4428
>Category: os-hpux
>Synopsis: Warning message during compile
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: apache
>State: open
>Class: support
>Submitter-Id: apache
>Arrival-Date: Mon May 17 06:30:02 PDT 1999
>Last-Modified:
>Originator: spcherub@koame001.delcoelect.com
>Organization:
apache
>Release: 1.3.6
>Environment:
HP-UX kofis001 B.10.20 A 9000/800
>Description:
I get the following warning message when I compile a default distribution.
(cd apache_1.3.6; ./configure; make)
cc: "ap_md5c.c", line 482: warning 604: Pointers are not assignment-compatible.
cc: "ap_md5c.c", line 482: warning 563: Argument #2 is not the correct type.
cc: "ap_md5c.c", line 487: warning 604: Pointers are not assignment-compatible.
cc: "ap_md5c.c", line 487: warning 563: Argument #2 is not the correct type.
cc: "ap_md5c.c", line 492: warning 604: Pointers are not assignment-compatible.
cc: "ap_md5c.c", line 492: warning 563: Argument #2 is not the correct type.
cc: "ap_md5c.c", line 498: warning 604: Pointers are not assignment-compatible.
cc: "ap_md5c.c", line 498: warning 563: Argument #2 is not the correct type.
cc: "ap_md5c.c", line 499: warning 604: Pointers are not assignment-compatible.
cc: "ap_md5c.c", line 499: warning 563: Argument #2 is not the correct type.
cc: "ap_md5c.c", line 500: warning 604: Pointers are not assignment-compatible.
cc: "ap_md5c.c", line 500: warning 563: Argument #2 is not the correct type.
cc: "ap_md5c.c", line 519: warning 604: Pointers are not assignment-compatible.
cc: "ap_md5c.c", line 519: warning 563: Argument #2 is not the correct type.
cc: "ap_md5c.c", line 541: warning 604: Pointers are not assignment-compatible.
cc: "ap_md5c.c", line 541: warning 563: Argument #2 is not the correct type.
cc: "ap_md5c.c", line 547: warning 604: Pointers are not assignment-compatible.
cc: "ap_md5c.c", line 547: warning 563: Argument #2 is not the correct type.
cc: "ap_md5c.c", line 551: warning 604: Pointers are not assignment-compatible.
cc: "ap_md5c.c", line 551: warning 563: Argument #2 is not the correct type.
cc: "ap_md5c.c", line 558: warning 604: Pointers are not assignment-compatible.
cc: "ap_md5c.c", line 558: warning 563: Argument #2 is not the correct type.
cc: "util.c", line 1028: warning 604: Pointers are not assignment-compatible.HSREGEX `../apaci
cc: "util.c", line 1037: warning 604: Pointers are not assignment-compatible.HSREGEX `../apaci
cc: "util_md5.c", line 117: warning 604: Pointers are not assignment-compatible.
cc: "util_md5.c", line 117: warning 563: Argument #1 is not the correct type.
>How-To-Repeat:
cd apache_1.3.6
./configure
make
>Fix:
I've had a preliminary look at one of the offending files "src/ap/ap_md5c.c"
On line 482 -> "ap_MD5Update(&ctx, pw, strlen(pw));"
variable "pw" is passed into the calling function as "const char *"
although decleration for function ap_MD5Update calls for a "AP_MD5_CTX *"
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED. This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig- ]
[nored unless you are responding to an explicit request ]
[from a developer. ]
[Reply only with text; DO NOT SEND ATTACHMENTS! ]