Summary: | --enable-layout never goes to apr apr-util | ||
---|---|---|---|
Product: | Apache httpd-2 | Reporter: | Jim Gifford <giffordj> |
Component: | Build | Assignee: | Apache HTTPD Bugs Mailing List <bugs> |
Status: | RESOLVED LATER | ||
Severity: | critical | CC: | poirier, rici |
Priority: | P3 | Keywords: | MassUpdate |
Version: | 2.0.47 | ||
Target Milestone: | --- | ||
Hardware: | Other | ||
OS: | Linux | ||
Attachments: |
Apr config.log
Config.log for apr-util custom config.layout config.log resulting from custom config.layout |
Description
Jim Gifford
2003-09-14 23:18:24 UTC
Created attachment 8220 [details]
Apr config.log
Created attachment 8221 [details]
Config.log for apr-util
Is this still reproducible with 2.0.53? Can you include your custom config.layout segment? No activity after a very long time in NEEDINFO; assuming expired. I am also experiencing this bug. My configure command is: `./configure --enable-layout=sf --enable-modules="deflate headers mime_magic rewrite ssl so" --disable-actions --disable-autoindex --disable-imap --disable-include --disable-negotiation --disable-setenvif --disable-status --disable-userdir` I have attached my config.layout and my config.log Created attachment 23274 [details]
custom config.layout
Created attachment 23275 [details]
config.log resulting from custom config.layout
It's slightly different however in that APR reports that bindir is NONE/bin, even though I set it properly. Can you double-check your config.layout? I tried it and ran into problems like bindir is set to $/usr/bin, and there are references to ${sfprefix} but sfprefix is never set anywhere. Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd. As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd. If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question. If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with. Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated. |