Executing apxs (from httpd 2.2.6) -q LIBEXEC returns an empty string. This was discovered during building of php-5.2.4 against httpd-2.2.6. It was caused by the variable libexecdir in config_vars.mk being assigned to ${libdir}/httpd. Changing the variable assignment to ${exec_prefix}/lib/httpd provides the expected result. Upon further investigation of the apxs script, apparently the get_vars() function was unable to perform proper variable substitution and adding the following modifications to the apxs script provides the solution: my $libdir = get_vars("libdir") my $CFG_LIBDIR = eval qq("$libdir") my %internal_vars = map {$_ => 1} qw(TARGET .. LIBDIR .. SYSCONFDIR); ^^^^^^ Can someone please check the modifications as I am not proficient in perl and was only guessing.
As of 2.2.22, apxs doesn't provide a value for LIBEXEC, but seems to provide a correct value for LIBEXECDIR (and the code in apxs looks like Mohamed Mirzar's in that case). From config.layout it looks like libexecdir is only derived from exec_prefix/prefix, not libdir. Is this bug fixed?
in 2.4.12 the problem still exist apcs -q libexecdir returns only a perl warning but no value. There is libexecdir derived from libdir
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.