On 14/01/2012 19:22, Dan Youngquist wrote:
On 01/14/2012 10:38 AM, Calvin Morrison wrote:
This bug is fixed in git. It was a libart issue. Will be there in R14
I have the same problem on 2 different machines -- the only 2 installs of 3.5.13 I've done so far -- and it's been reported on the list at least twice since then. So I think it must be a common problem that lots of folks run into. I haven't tried the patch yet, but am about to do so.
But most who get to the website, install Trinity, and have this problem won't know there's a patch -- they'll just see a great big bug that's still there, and uninstall Trinity and never try it again. So I think it's a really bad idea to leave it unfixed until R14.
Ok, guys, thanks for the info. I probably should have searched a bit more before posting.
I'll track down the patch and see how things go.