On 25 Oct2017, at 1:18 PM, Rainer Müller <[email protected]> wrote:
>
> On 2017-10-25 16:57, Murray Eisenberg wrote:
>> Since upgrading from apache 2.2 to apache 2.4, whenever I do a “sudo
>> port upgrade…” or “sudo port install…”, at the end I see:
>>
>> ---> Updating database of binaries
>> ---> Scanning binaries for linking errors
>> Warning: Error parsing file /opt/local/apache2/libexec/mod_perl.so:
>> Error opening or reading file
>> Warning: Error parsing file /opt/local/apache2/modules/mod_perl.so:
>> Error opening or reading file
>> ---> No broken files found.
>>
>> fromWith apache 2.4, there seems to be no directory /op/local/apache2 at
>> all (unless it should still be there and I inadvertently removed it).
>>
>> What’s wrong?
>
> This looks like /opt/local/apache2/modules/mod_perl.so is in the
> registry as installed and active, but it does not exist in the filesystem.
>
> Does 'port provides /opt/local/apache2/modules/mod_perl.so' show which
> port it is meant to belong to? And which port does the other mone at
> /opt/local/lib/apache2/modules/mod_perl.so belong to?
>
> I assume something went wrong with mod_perl2 when it was updated for
> apache2 @2.4.x.
>
> Rainer
Output from
port provides /opt/local/apache2/modules/mod_perl.so
is:
/opt/local/apache2/modules/mod_perl.so does not exist.
Output from
port provides /opt/local/lib/apache2/modules/mod_perl.so
is:
/opt/local/lib/apache2/modules/mod_perl.so is not provided by a MacPorts
port.
Yet
/opt/local/lib/apache2/modules/mod_perl.so
exists.
---
Murray Eisenberg [email protected]
503 King Farm Blvd #101 Home (240)-246-7240
Rockville, MD 20850-6667 Mobile (413)-427-5334
