Bug 14922 - <target> is currently hardcoded to 'apache2'
Summary: <target> is currently hardcoded to 'apache2'
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Build (show other bugs)
Version: 2.0.43
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2002-11-28 09:44 UTC by ian stuart
Modified: 2018-11-07 21:07 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description ian stuart 2002-11-28 09:44:38 UTC
This "feature" requires that multiple layouts are required in a config.layout
file when building multiple httpd systems.

Please allow this value to accept a value entered, say from the
"--with-program-name=foo" option.

It would probably be prudent to re-instate the "--show-layout" option as well,
so that the layout can be reviewed.

This would give the 2.0.x series one of the great features that is in the 1.3.x
Comment 1 Thom May 2002-11-28 15:18:04 UTC
Um, I'm really sorry, but I don't quite get what you're asking for here:
)--enable-layout should be used to specify which layout you desire
)you can mix layouts and prefix directives, ie: --with-layout=Debian

If this isn't what you mean, sorry :-) Please could you clarify?

I'll look into adding --show-layout to apache2

Thanks for using Apache!
Comment 2 ian stuart 2002-11-28 16:28:01 UTC
With apache 1.3.x, the config.layout used a syntax such as:
    datadir:       ${prefix}/share+
and the installation then created a subdirectory ${prefix}/share/<foo>, where
foo was some derived from a parameter (--target, which is no longer available
'cos of the switch to autoconf)

There are some notes in the comments at the top of the config.layout file itself.
Comment 3 Thom May 2002-11-28 17:30:35 UTC
OK, understood now! 
Comment 4 Davi Arnaut 2007-06-08 12:19:21 UTC
Is the issue still a problem?
Comment 5 William A. Rowe Jr. 2018-11-07 21:07:59 UTC
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.