>Number:         3381
>Category:       os-aix
>Synopsis:       Compilation warnings
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Nov 11 06:40:01 PST 1998
>Last-Modified:
>Originator:     [EMAIL PROTECTED]
>Organization:
apache
>Release:        1.3.3
>Environment:
AIX 4.3.1
GCC 2.8.1
uname -a="AIX neve 3 4 000175A24C00"
>Description:
After configuring with

        DFLAGS=_LONG_LONG; ./configure     # see PR#3379

almost all files that was compiled got this warnings:

In file included from ../include/ap_config.h:919,
                 from logresolve.c:42:
/usr/include/arpa/inet.h:152: warning: `struct ether_addr' declared inside 
parameter list
/usr/include/arpa/inet.h:152: warning: its scope is only this definition or 
declaration,
/usr/include/arpa/inet.h:152: warning: which is probably not what you want.
/usr/include/arpa/inet.h:153: warning: `struct ether_addr' declared inside 
parameter list
/usr/include/arpa/inet.h:154: warning: `struct ether_addr' declared inside 
parameter list
/usr/include/arpa/inet.h:159: warning: `struct sockaddr_dl' declared inside 
parameter list
/usr/include/arpa/inet.h:160: warning: `struct sockaddr_dl' declared inside 
parameter list
/usr/include/arpa/inet.h:161: warning: `struct sockaddr_dl' declared inside 
parameter list

The web-server seems to run well even with this warnings.
When I compiled with C for AIX v4.4 (the IBM compiler), I didn't get any
compilation problem but I couldn't run it well (PR#2534)
>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. ]
[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!         ]



Reply via email to