Re: [RFC] APXS LoadModule Option in configure
| From: | Kris Craig | Date: | Sat, 25 Feb 2012 00:14:28 +0000 |
| Subject: | Re: [RFC] APXS LoadModule Option in configure | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-58057@lists.php.net to get a copy of this message | ||
No, it happens and it's even clearly documented in APXS.
Basically, if you specify the "-a" option in APXS, it overwrites your
httpd.conf (or apache.conf or whatever it is on your system) and adds the
LoadModule line to it. In PHP's configure script, you'll notice that "-a"
is always specified; there's no option to use APXS without it. As a
result, "make install" will always overwrite your LoadModule entry in
httpd.conf if APXS is enabled. The problem occurs when you have LoadModule
in an included .conf file already; APXS does not have the ability to detect
that. Therefore, a "duplicate" LoadModule entry is added to httpd.conf by
APXS, and thus the clash occurs. This behavior has been reproduced
numerous times.
I think the RFC is pretty clear on how this works. Nobody else has
expressed confusion thus far. I could clarify further but I'm not sure
how; it's pretty straight-forward, really. I'm not sure what may have been
happening in your case or if perhaps you misunderstood what this RFC is
about. Either way, I would recommend you create a fresh Linux-based build
environment, build Apache 2.2 and PHP 5.3.10 yourself (i.e. stay away from
yum/apt-get), then attempt to generate an APXS-enabled Makefile using PHP's
configure script that does not activate APXS with the "-a" option. It
might also be a good idea for you to check-out the APXS documentation (I
included a link to it on the RFC).
Those steps should enable you to reproduce this. =)
--Kris
On Fri, Feb 24, 2012 at 4:02 PM, Christopher Jones <
christopher.jones@oracle.com> wrote:
>
> On 02/24/2012 03:54 PM, Kris Craig wrote:
>
>> LoadModule clashes still happen in the current releases. I haven't
>> tested it on 5.5-dev but it definitely exists on 5.3.x. I have yet
>> to test it on 5.4 but I'm not aware of any changes there that
>> would've affected this. So this is an existing problem,
>>
>
> It doesn't happen for me and I frequently build PHP 5.3, 5.4 and trunk
> mods. The library name is the same for all branches. Are you sure
> it's not a feature/bug of your APXS version? Anyway, the RFC needs
> more investigative description, IMHO.
>
> Chirs
>
>
> --
> Email: christopher.jones@oracle.com
> Tel: +1 650 506 8630
> Blog: http://blogs.oracle.com/opal/
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>