On Aug 11, 2017, at 01:21, Barrie Stott wrote:
> I don’t remember having a problem with the lout port until I moved to Sierra.
> Now all my ports are fine except lout.
Could you be more specific about what doesn't work?
Hi,
Some of you may have seen that I've uploaded an update to port:openal-soft to
trac, bringing the port to the current v1.18.1 . I've also filed a ticket for a
build conflict in Qt5's QtMultiMedia component, which is supposed to build
against the system OpenAL.framework but which picks up
indeed, without the full log cant tell what is wrong.
Best, K
> On Aug 11, 2017, at 10:41 AM, Barrie Stott wrote:
>
>> On 11 Aug 2017, at 08:52, Ryan Schmidt wrote:
>>
>>> On Aug 11, 2017, at 01:21, Barrie Stott wrote:
>>>
>>> I don’t remember
I don’t remember having a problem with the lout port until I moved to Sierra.
Now all my ports are fine except lout.
Barrie.
> On 11 Aug 2017, at 09:50, Ken Cunningham
> wrote:
>
> indeed, without the full log cant tell what is wrong.
>
> Best, K
Sorry about that. Here is the full log.
Barrie.
main.log
Description: Binary data
> On Aug 11, 2017, at 10:41 AM, Barrie Stott
I see that Apache 2.2 officially hit EOL as of the latest release (7/11/17).
Any chance we'll see an Apache 2.4 for production in MacPorts in the
near future?
thanks
--
Bill Christensen
http://SustainableSources.com
http://LinkedIn.com/in/billc108
On 2017-08-11, at 2:14 AM, Barrie Stott wrote:
>> On 11 Aug 2017, at 09:50, Ken Cunningham
>> wrote:
>>
>> indeed, without the full log cant tell what is wrong.
>>
>> Best, K
>
> Sorry about that. Here is the full log.
>
> Barrie.
>
First of all, the port