I think I have the same problem and I limited myself to python3.5.4
I did not find any clues about the problem either.
LP
> Le 5 janv. 2018 à 13:35, Ryan Schmidt a écrit :
>
>
> On Jan 5, 2018, at 06:11, Clayson wrote:
>
>> Dear Ryan,
>>
>> Have you had a chance to
On Fri, 5 Jan 2018, Ryan Schmidt wrote:
If you have been using perl5.24 and p5.24 modules for your own projects
and now want to use perl5.26, simply install the p5.26 versions of the
modules you want.
Err, why should a user have to waste disk space on two versions of Perl?
Surely if a port
Hi Ken,
Riccardo Mottola via macports-users wrote:
I actually use a different one, it is not commited (*), I attach it here.
It disables several problematic features: The goal is currently to "finish the
build" and see if we start up the browser.
Slowly we can then debug enable things again,
On Jan 5, 2018, at 17:49, Dave Horsfall wrote:
> On Fri, 5 Jan 2018, Ryan Schmidt wrote:
>
>> If you have been using perl5.24 and p5.24 modules for your own projects and
>> now want to use perl5.26, simply install the p5.26 versions of the modules
>> you want.
>
> Err, why should a user have
There's no problem here. Just because ports use perl5.24 or perl5.26 for their
own purposes has no bearing on what you use for your own personal projects.
perl5.24 and perl5.26 install to different locations, do not conflict with one
another, and can be simultaneously installed and used.
On Jan 5, 2018, at 06:11, Clayson wrote:
> Dear Ryan,
>
> Have you had a chance to look at this? I’ve been told by several rresponders
> to my qurestion that Quartz is of course in ALL recent Mac system BUT my
> question was not that.
>
> Instead I was asking about: when I install python
In case anyone hasn't heard of it yet,
https://meltdownattack.com/
https://lwn.net/Articles/742999/
Hey folks,
for Meltdown, MacOS 10.13.2 is already patched and secure.
As for Spectre, LLVM developers have committed a workaround (it’s a bit complex
to detail here) for 5/6 which should be back ported. Whomever is responsible
for LLVM should be on the lookout for the new versions to appear