Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58057
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.170 as permitted sender)
Received-SPF: pass (google.com: domain of kris.craig@gmail.com designates 10.216.132.32 as permitted sender) client-ip=10.216.132.32;
MIME-Version: 1.0
In-Reply-To: <4F482524.6060106@oracle.com>
References: <CAKOpQSwMkn=0cQh9cupj-8qihVvhEEOY-kqQ0F4pLb4J1MfuZA@mail.gmail.com>
	<a0f321a49cb0932bde8bba4adc890bca.squirrel@www.l-i-e.com>
	<CAKOpQSwYa89n3s8FzytQ49i8MqUA9sFsQRh+enGzADg=h4A4xg@mail.gmail.com>
	<4F481E93.1090400@oracle.com>
	<CAKOpQSzRdjqThrTb6JeEzhnKmg_85WKejicN1rhMp49+v6cjHg@mail.gmail.com>
	<4F482524.6060106@oracle.com>
Date: Fri, 24 Feb 2012 16:14:28 -0800
Message-ID: <CAKOpQSyn8LtbBWor5ywo=hLkauSECf6shEvp9LKcrXcb9ZRnZA@mail.gmail.com>
To: Christopher Jones <christopher.jones@oracle.com>
Cc: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=0016e6d7ef29bb4d1904b9bec2e1
Subject: Re: [PHP-DEV] [RFC] APXS LoadModule Option in configure
From: kris.craig@gmail.com (Kris Craig)

--0016e6d7ef29bb4d1904b9bec2e1
Content-Type: text/plain; charset=ISO-8859-1

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
>
>

--0016e6d7ef29bb4d1904b9bec2e1--