>Number: 4370
>Category: config
>Synopsis: Make warns about incompatible pointer assignments and
>conversions
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: apache
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Fri May 7 13:50:01 PDT 1999
>Last-Modified:
>Originator: [EMAIL PROTECTED]
>Organization:
apache
>Release: 1.3.6
>Environment:
Ultrix 4.4 on DEC 5240 (MIPS) using DEC's "cc" compiler
uname -a = ULTRIX rccnx1 4.4 0 RISC
>Description:
# make
===> src
===> src/regex
cc -I. -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
-DPOSIX_MISTAKE -c regcomp.c
cc -I. -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
-DPOSIX_MISTAKE -c regexec.c
cc -I. -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
-DPOSIX_MISTAKE -c regerror.c
cc -I. -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
-DPOSIX_MISTAKE -c regfree.c
rm -f libregex.a
ar cr libregex.a regcomp.o regexec.o regerror.o regfree.o
ranlib libregex.a
<=== src/regex
===> src/os/unix
cc -c -I../../os/unix -I../../include -DULTRIX -std -DUSE_HSREGEX
`../../apaci` os.c
cc -c -I../../os/unix -I../../include -DULTRIX -std -DUSE_HSREGEX
`../../apaci` os-inline.c
rm -f libos.a
ar cr libos.a os.o os-inline.o
ranlib libos.a
<=== src/os/unix
===> src/ap
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci` ap_exe
cve.c
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
ap_cpystrn.c
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
ap_signal.c
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
ap_slack.c
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
ap_snprintf.c
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
ap_fnmatch.c
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
ap_md5c.c
cfe: Warning: ap_md5c.c, line 482: Incompatible pointer type assignment
ap_MD5Update(&ctx, pw, strlen(pw));
-----------------------^
cfe: Warning: ap_md5c.c, line 487: Incompatible pointer type assignment
ap_MD5Update(&ctx, apr1_id, strlen(apr1_id));
-----------------------^
cfe: Warning: ap_md5c.c, line 492: Incompatible pointer type assignment
ap_MD5Update(&ctx, sp, sl);
-----------------------^
cfe: Warning: ap_md5c.c, line 498: Incompatible pointer type assignment
ap_MD5Update(&ctx1, pw, strlen(pw));
------------------------^
cfe: Warning: ap_md5c.c, line 499: Incompatible pointer type assignment
ap_MD5Update(&ctx1, sp, sl);
------------------------^
cfe: Warning: ap_md5c.c, line 500: Incompatible pointer type assignment
ap_MD5Update(&ctx1, pw, strlen(pw));
------------------------^
cfe: Warning: ap_md5c.c, line 519: Incompatible pointer type assignment
ap_MD5Update(&ctx, pw, 1);
-----------------------^
cfe: Warning: ap_md5c.c, line 541: Incompatible pointer type assignment
ap_MD5Update(&ctx1, pw, strlen(pw));
------------------------^
cfe: Warning: ap_md5c.c, line 547: Incompatible pointer type assignment
ap_MD5Update(&ctx1, sp, sl);
------------------------^
cfe: Warning: ap_md5c.c, line 551: Incompatible pointer type assignment
ap_MD5Update(&ctx1, pw, strlen(pw));
------------------------^
cfe: Warning: ap_md5c.c, line 558: Incompatible pointer type assignment
ap_MD5Update(&ctx1, pw, strlen(pw));
------------------------^
cfe: Warning: ap_md5c.c, line 606: illegal combination of pointer and integer
crypt_pw = crypt(passwd, hash);
---------^
rm -f libap.a
ar cr libap.a ap_execve.o ap_cpystrn.o ap_signal.o ap_slack.o ap_snprintf.o ap_
fnmatch.o ap_md5c.o
ranlib libap.a
<=== src/ap
===> src/main
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
gen_test_char.c
cc -DULTRIX -std -DUSE_HSREGEX `../apaci` -o gen_test_char gen_test_char.o
./gen_test_char >test_char.h
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
gen_uri_delims.c
cc -DULTRIX -std -DUSE_HSREGEX `../apaci` -o gen_uri_delims gen_uri_delims.o
./gen_uri_delims >uri_delims.h
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
alloc.c
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci` buff.c
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
http_config.c
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
http_core.c
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
http_log.c
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
http_main.c
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
http_protocol.c
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
http_request.c
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
http_vhost.c
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci` util.c
cfe: Warning: util.c, line 1028: Incompatible pointer type assignment
*field = ptr;
---------------^
cfe: Warning: util.c, line 1037: Incompatible pointer type assignment
*field = ptr;
-----------^
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
util_date.c
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
util_script.c
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
util_uri.c
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
util_md5.c
cfe: Warning: util_md5.c, line 117: Incompatible pointer type assignment
return ap_md5_binary(p, string, strlen(string));
-------------------------------------------^
cc -c -I../os/unix -I../include -DULTRIX -std -DUSE_HSREGEX `../apaci`
rfc1413.c
rm -f libmain.a
ar cr libmain.a alloc.o buff.o http_config.o http_core.o http_log.o http_main.
o http_protocol.o http_request.o http_vhost.o util.o util_date.o util_script.o
util_uri.o util_md5.o rfc1413.o
ranlib libmain.a
<=== src/main
===> src/modules
===> src/modules/standard
cc -c -I../../os/unix -I../../include -DULTRIX -std -DUSE_HSREGEX
`../../apaci` mod_env.c
cc -c -I../../os/unix -I../../include -DULTRIX -std -DUSE_HSREGEX
`../../apaci` mod_log_config.c
cc -c -I../../os/unix -I../../include -DULTRIX -std -DUSE_HSREGEX
`../../apaci` mod_mime.c
cc -c -I../../os/unix -I../../include -DULTRIX -std -DUSE_HSREGEX
`../../apaci` mod_negotiation.c
cc -c -I../../os/unix -I../../include -DULTRIX -std -DUSE_HSREGEX
`../../apaci` mod_status.c
cc -c -I../../os/unix -I../../include -DULTRIX -std -DUSE_HSREGEX
`../../apaci` mod_include.c
cc -c -I../../os/unix -I../../include -DULTRIX -std -DUSE_HSREGEX
`../../apaci` mod_autoindex.c
cc -c -I../../os/unix -I../../include -DULTRIX -std -DUSE_HSREGEX
`../../apaci` mod_dir.c
cc -c -I../../os/unix -I../../include -DULTRIX -std -DUSE_HSREGEX
`../../apaci` mod_cgi.c
cc -c -I../../os/unix -I../../include -DULTRIX -std -DUSE_HSREGEX
`../../apaci` mod_asis.c
cc -c -I../../os/unix -I../../include -DULTRIX -std -DUSE_HSREGEX
`../../apaci` mod_imap.c
cc -c -I../../os/unix -I../../include -DULTRIX -std -DUSE_HSREGEX
`../../apaci` mod_actions.c
cc -c -I../../os/unix -I../../include -DULTRIX -std -DUSE_HSREGEX
`../../apaci` mod_userdir.c
cc -c -I../../os/unix -I../../include -DULTRIX -std -DUSE_HSREGEX
`../../apaci` mod_alias.c
cc -c -I../../os/unix -I../../include -DULTRIX -std -DUSE_HSREGEX
`../../apaci` mod_access.c
cc -c -I../../os/unix -I../../include -DULTRIX -std -DUSE_HSREGEX
`../../apaci` mod_auth.c
cc -c -I../../os/unix -I../../include -DULTRIX -std -DUSE_HSREGEX
`../../apaci` mod_setenvif.c
rm -f libstandard.a
ar cr libstandard.a mod_env.o mod_log_config.o mod_mime.o mod_negotiation.o mod_
status.o mod_include.o mod_autoindex.o mod_dir.o mod_cgi.o mod_asis.o mod_imap.o
mod_actions.o mod_userdir.o mod_alias.o mod_access.o mod_auth.o mod_setenvif.o
ar: Info: filename mod_log_config.o truncated to mod_log_config.
ar: Info: filename mod_negotiation.o truncated to mod_negotiation
ranlib libstandard.a
<=== src/modules/standard
*** Error code 1
Stop.
>How-To-Repeat:
Just make Apache 1.3.6 with *no* SSL or other additional modules on Ultrix 4.4.
>Fix:
No, but you guys have seen this before as PR 958 (now closed). For that PR,
[EMAIL PROTECTED] said "Without access to various ultrix platforms it'll be
hard to
eliminate the warnings reliably. So for now we'll just have to live with them."
So here is the result on another Ultrix platform at a different Apache release.
Please ignore the failure in "ar" at the end of the above trace - I'll log that
as a separate PR.
Sorry if there's nothing you can do - please just close this PR. But I'd
appreciate knowing whether or not the warnings "matter". Or even whether you
think I'd get a clean(er) build if I used GCC instead of DEC's compiler.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <[EMAIL PROTECTED]> 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! ]
