>Number: 1685
>Category: mod_imap
>Synopsis: compiler warnings for mod_imap (not seen with e.g. Apache
>1.2.3)
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: apache
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Fri Jan 16 06:40:00 PST 1998
>Last-Modified:
>Originator: [EMAIL PROTECTED]
>Organization:
apache
>Release: 1.2.5
>Environment:
Sun - Solaris 2.4 (SPARC), with Sun's C compiler V4.0
>Description:
The C compiler is reporting
"mod_imap.c", line 766: warning: argument #2 is incompatible with prototype:
prototype: pointer to array[2] of const double : "mod_imap.c", line 198
argument : pointer to array[2] of double
"mod_imap.c", line 778: warning: argument #2 is incompatible with prototype:
prototype: pointer to array[2] of const double : "mod_imap.c", line 185
argument : pointer to array[2] of double
"mod_imap.c", line 790: warning: argument #2 is incompatible with prototype:
prototype: pointer to array[2] of const double : "mod_imap.c", line 160
argument : pointer to array[2] of double
"mod_imap.c", line 802: warning: argument #2 is incompatible with prototype:
prototype: pointer to array[2] of const double : "mod_imap.c", line 273
argument : pointer to array[2] of double
This looks like the same problem as PR#1650, but on different hardware and with
a different compiler. If it's really the compiler being silly (as suggested for
PR#1650), rather than incorrect code, it's not specific to a single compiler or
system type...
>How-To-Repeat:
>Fix:
>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. ]
