> On 5 Apr 2019, at 21:43, Makarius <[email protected]> wrote: > > On 05/04/2019 17:30, Traytel Dmitriy wrote: >> >> I have the same problem as Jasmin (on a MacBook Pro running macOS 10.14.3). >> >> I can build Isabelle2018 (also from the repository via hg update -r >> Isabelle2018). >> >> Stack Trace >> main [1] (RUNNABLE) >> scala.tools.nsc.ast.Trees.newStrictTreeCopier line: 108 >> scala.tools.nsc.ast.Trees.newStrictTreeCopier$ line: 108 >> scala.tools.nsc.Global.newStrictTreeCopier line: 44 >> scala.tools.nsc.Global.newStrictTreeCopier line: 44 > > This is the Scala compiler -- the "nsc" package refers to the "new scala > compiler". > > Some years ago we have had a similar situation where Scala-generated > Java Byte Code did not work properly on certain multicore Macs. Here the > compiler itself gets into problems, but it also consists of > Scala-generated Java Byte Code. > > I have presently two mac Minis available for testing, of quite different > age. Both are running current macOS 10.14.4, and both can build > "isabelle jedit -b -f" with current tip 9b34dbeb1103. > > So I cannot do anything right now -- it works for me on my hardware. > > > Since you manage to build Isabelle2018, you could run "hg bisect" to > find the problem in the history. This will be a bit time-consuming, though. > > Note that you need to run "isabelle components -a" and a strict > "isabelle jedit -b -f" in every step.
Instead of bisect, I took an educated guess after looking at the file history of Admin/components/main. So the first bad commit for me is b578749daa62 (which introduces scala 2.12.8). With its parent isabelle jedit -bf works. Funnily, my operating system installation of scala is 2.12.8 too and I don't have any problems with it. Not sure how to proceed from here. Dmitriy _______________________________________________ isabelle-dev mailing list [email protected] https://mailman46.in.tum.de/mailman/listinfo/isabelle-dev
