Apache 2.4.28 update today? (was:Re: Apache 2.4 any time soon?)

[Bill Christensen]

Guess I'll just have to dig an earlier version out of a backup so I can 
continue w/ 2.2 for a little bit, until I'm sure on the setup of 2.4

On 10/19/17 3:23 PM, Marius Schamschula wrote:
> Bill,
>
> php’s apache2handler is built against a specific version of apache. 
> Now this defaults to version 2.4.x. Thus you can’t just copy the model 
> over to apache 2.2 and expect it to work.
>
> The only way to get around this is to use php-fpm and and some flavor 
> of fastcgi, which will work with multiple versions of apache. I 
> haven’t had the time to get this combination working under apache, but 
> I use this approach with nginx (there is no other choice, as there is 
> no equivalent to apache2handler for nginx).
>
>
>> On Oct 19, 2017, at 2:55 PM, Bill Christensen 
>> <billc_lists at greenbuilder.com <mailto:billc_lists at greenbuilder.com>> 
>> wrote:
>>
>> Problem:
>>
>> I originally ran the update to Apache 2.4, then quickly changed the 
>> active Apache version back to 2.2 as I had not yet tested everything 
>> out.
>>
>> I'm still running php70, and I found that mod_php70.so had been moved 
>> to the new modules directory (/opt/local/lib/apache2/modules/).  
>> Everything worked fine when I moved it back to the original modules 
>> directory (/opt/local/apache2/modules/).
>>
>> Now, a couple days later and having run some other updates (libcomerr 
>> and php70_apache2handler). I once again found mod_php70.so in the new 
>> directory and not in the old.  This time I made a copy, so it's in 
>> both places.
>>
>> When I run configtest now, I see:
>>
>> Cannot load /opt/local/apache2/modules/mod_php70.so into server: 
>> dlopen(/opt/local/apache2/modules/mod_php70.so, 10): Symbol not 
>> found: _ap_unixd_config\nReferenced from: 
>> /opt/local/apache2/modules/mod_php70.so\nExpected in: 
>> /opt/local/apache2/bin/httpd\n in /opt/local/apache2/modules/mod_php70.so
>>
>>
>> Pointers as to what to do next?
>>
>>
>> Thanks.
>>
>>
>> On Mon, Oct 16, 2017 at 10:48 AM, Marius Schamschula 
>> <lists at schamschula.com <mailto:lists at schamschula.com>> wrote:
>>
>>     Done in
>>     https://github.com/macports/macports-ports/commit/1e70102f38315d1bfaa0d08401b3c41daf7e2dd7
>>     <https://github.com/macports/macports-ports/commit/1e70102f38315d1bfaa0d08401b3c41daf7e2dd7>
>>
>>     Also there are useful transition notes under
>>     https://trac.macports.org/ticket/50965#comment:18
>>     <https://trac.macports.org/ticket/50965#comment:18>
>>
>>>     Well, the old apache2 installed everything under
>>>     ${prefix}/apache2, which violated the MacPorts tree. The new
>>>     version installs things under:
>>>
>>>     1) configuration - ${prefix}/etc/apache2/
>>>
>>>     2) data - ${prefix}/www/
>>>
>>>     3) binaries - ${prefix}/sbin
>>>
>>>     4) modules -  ${prefix}/lib/apache2/modules
>>>
>>>     I had meant add a note to the Portfile. I will add this.
>>
>>     Marius
>>     --
>>     Marius Schamschula
>>
>>
>
> Marius
> --
> Marius Schamschula
>

-- 
Bill Christensen
http://SustainableSources.com
http://LinkedIn.com/in/billc108

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20171020/04fda279/attachment.html>