Bjarne,
The problem with running “grep 'fatal error'” is that you see things out of
context.
> On Oct 30, 2017, at 4:48 PM, Bjarne D Mathiesen
> wrote:
>
> I'm seeing this for both
> php55-apache2handler
> php71-apache2handler
>
> Does anybody have any idea as to
> what's g
I'm seeing this for both
php55-apache2handler
php71-apache2handler
Does anybody have any idea as to
what's going on
how to solve this
???
MacPro: root# port -f clean --all php71-apache2handler
---> Cleaning php71-apache2handler
MacPro: root# port upgrade php71-ap
On Oct 30, 2017, at 12:18 PM, Ken Cunningham
wrote:
> As you probably know, homebrew runs it's entire operation that way,
> symlinking into /usr/local.
homebrew has over its history followed a similar path that MacPorts has
(re-learning many of the same lessons). I don't know if they've fixed
As you probably know, homebrew runs it's entire operation that way, symlinking
into /usr/local.
> On Oct 30, 2017, at 8:29 AM, Daniel J. Luke wrote:
>
>> On Oct 27, 2017, at 8:33 PM, Ryan Schmidt wrote:
>> I don't know if anything will break if you use symlinks; I would expect most
>> ports w
On Oct 27, 2017, at 8:33 PM, Ryan Schmidt wrote:
> I don't know if anything will break if you use symlinks; I would expect most
> ports would work but some might not.
Long ago, macports used to use symlinks in some cases to activate ports. It did
mostly work, but the cases where it didn't were
