You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Hugh Stewart <Hu...@acm.org> on 2001/08/04 15:32:46 UTC

build/8136: Warnings in compiling system include files made configure fail

>Number:         8136
>Category:       build
>Synopsis:       Warnings in compiling system include files made configure fail
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sat Aug 04 06:40:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Hugh.Stewart@acm.org
>Release:        2.0.18
>Organization:
apache
>Environment:
HP-UX sdlhpp41 B.11.00 A 9000/780 
>Description:
I attempted to build on HP and when I ran ./configure it gave up when the 
unix/mm/configure file was checking for valid system include files

The test boiled down to generating this file:-
#line 1144 "configure"
#include "confdefs.h"
#include <$ac_hdr>

and seeing if $CPP would run on it without generating any errors.

On my machine $CPP turned into gcc -E but the (HP supplied) stdlib.h generated
this warning:-

[69]  gcc -E  conftest.c >/dev/null
In file included from /usr/include/sys/resource.h:26,
                 from /tool_shed/gccnew/lib/gcc-lib/hppa1.1-hp-hpux10.20/2.7.2.1/include/sys/wait.h:83,
                 from /tool_shed/gccnew/lib/gcc-lib/hppa1.1-hp-hpux10.20/2.7.2.1/include/stdlib.h:231,
                 from configure:1145:
/tool_shed/gccnew/lib/gcc-lib/hppa1.1-hp-hpux10.20/2.7.2.1/include/sys/time.h:492: warning: `FD_ISSET' redefined
/usr/include/sys/_fd_macros.h:72: warning: this is the location of the previous definition




>How-To-Repeat:
Try autoconfiguring on HP-UX 11
>Fix:
I cured it by changing the $CPPFLAGS to -E -w  to suppress the warnings 
>Release-Note:
>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!     ]