With the workaround, when you set OBJC_DISABLE_INITIALIZE_FORK_SAFETY, it must be set to YES, not yes. Which way did you try it?
John On Monday, December 17, 2018 at 1:56:38 PM UTC-8, Justin C. Walker wrote: > > > > > On Dec 16, 2018, at 14:35 , Volker Braun <vbrau...@gmail.com > <javascript:>> wrote: > > > > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the self-contained source tarball is at > http://www.sagemath.org/download-latest.html > > Built w/o problems, from a fresh clone of the develop tree, on two macOS > systems. > > 10.13.6 (2017 iMac Pro, Xeon W): testing (‘ptestlong’) yielded two > failures: > sage -t --long --warn-long 57.7 src/sage/combinat/designs/ext_rep.py # > Killed due to abort > sage -t --long --warn-long 57.7 src/sage/doctest/external.py # Killed due > to abort > > The discussion in #25921 indicates that these are due to the issue with > fork/exec in Obj-C code. The “workaround” suggested doesn’t work for > either of these in my case. Using “OBJC_DISABLE… sage -t …”, I still get > an immediate abort in both cases. > > 10.11.6 (mid-2015 MBP, Quad-core Core i7): testing (‘ptestlong’) had all > tests passing. > > Justin > > -- > Justin C. Walker, Curmudgeon-At-Large > Institute for the Absorption of Federal Funds > -------- > Men are from Earth. > Women are from Earth. > Deal with it. > -------- > > > > -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
