> On 17 Jan 2021, at 23:08, Daniel J. Luke wrote:
>
> On Jan 17, 2021, at 7:51 AM, Steve Wardle via macports-users
> wrote:
>>> I figured out why this is happening and filed a bug report for you:
>>>
>>> https://bz.apache.org/bugzilla/show_bug.cgi?id=65087
>>>
>>> It's a bug in the apr
On Jan 17, 2021, at 7:51 AM, Steve Wardle via macports-users
wrote:
>> I figured out why this is happening and filed a bug report for you:
>>
>> https://bz.apache.org/bugzilla/show_bug.cgi?id=65087
>>
>> It's a bug in the apr configure script. apr is a library that apache uses.
>
> Thanks
> On 17 Jan 2021, at 09:16, Ryan Schmidt wrote:
>
> On Jan 12, 2021, at 02:31, Steve Wardle wrote:
>
>> On 12 Jan 2021, at 01:37, Ryan Schmidt wrote:
>>
>>> On Jan 9, 2021, at 12:16, Steve Wardle wrote:
>>>
I’ve got apache2 2.4.46 running on Big Sur 11.1 and it’s not listening on
On Jan 12, 2021, at 02:31, Steve Wardle wrote:
> On 12 Jan 2021, at 01:37, Ryan Schmidt wrote:
>
>> On Jan 9, 2021, at 12:16, Steve Wardle wrote:
>>
>>> I’ve got apache2 2.4.46 running on Big Sur 11.1 and it’s not listening on
>>> the IPv6 interfaces. I’m sure this was working last year and it
On Jan 12, 2021, at 00:34, raf wrote:
> I treated this like a migration, recorded and uninstalled existing ports,
> then installed/upgraded macports, and then restored the ports.
>
> Mac OS X 10.6 (darwin/10.8.0) arch i386
> MacPorts 2.6.4
> Xcode 3.2.6
> SDK 10.6
>
