You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Gary Bickford <ga...@fxt.com> on 1999/09/22 23:22:13 UTC
general/5053: incompatible type in indirect function reference - compile fails for http_main.c
>Number: 5053
>Category: general
>Synopsis: incompatible type in indirect function reference - compile fails for http_main.c
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: apache
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Wed Sep 22 14:30:02 PDT 1999
>Last-Modified:
>Originator: garyb@fxt.com
>Organization:
apache
>Release: 1.3.9
>Environment:
NeXT Mach 3.3: Mon Oct 24 13:56:37 PDT 1994; root(rcbuilder):mk-171.9.obj~2/RC_m68k/RELEASE_M68K
gcc 2.8.1, make 3.77, associated libraries installed
>Description:
using 'gcc -c -I../os/unix -I../include -O -DNEXT -DUSE_HSREGEX -DUSE_EXPAT -I../lib/expat-lite http_main.c
I get some warnings in the 2.8.1/include/bsd/netinet/ip.h, then I get fatal errors like this:
http_main.c: In function `ap_unregister_other_child':
http_main.c:1504: incompatible type for argument 3 of indirect function call
Same error at lines 1560, 2366, 2369, 2375
>How-To-Repeat:
Same error on 1.3.6, haven't tried elsewhere.
>Fix:
Outside my competence, but can the correct argument be cast to the desired type? I tried tracking this down but I'm not up on my C/C++ these days.
>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 make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or ]
["Re: general/1098:"). If the subject doesn't match this ]
[pattern, your message will be misfiled and ignored. The ]
["apbugs" address is not added to the Cc line of messages from ]
[the database 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! ]