>Number: 5079 >Category: general >Synopsis: make install should not put include files into the "global >namespace". >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: open >Class: change-request >Submitter-Id: apache >Arrival-Date: Wed Sep 29 05:30:00 PDT 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.x >Environment: Not relevant. >Description: When doing "make install", apache copies a set of include files into the directory $(PREFIX)/include. This is somewhat dangerous since you have include files with very general names like "alloc.h", "compat.h", or "os.h".
On some systems this may overwrite system headers when Apache has been compiled with --prefix=/usr --- what some people do, notably under Linux. >How-To-Repeat: >Fix: IMHO it would be better to put the includes into a directory $(PREFIX)/include/apache and to access them as <apache/alloc.h>, like X11 includes do, for example. This also had the advantage that linking from /usr/include/apache (or some other place) to the real include directory will enable programs to find the apache includes without needing additional -I... statements at compile time. >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 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! ]
