On Wednesday, August 3, 2016 at 3:07:55 PM UTC, Bill Hart wrote: > > I got the Windows 10 anniversary update and turned on the new Windows > subsystem for Linux. >
[You mean the subsystem and bash is no non-beta/Insder program, good to know, and useful for software that isn't already portable to Windows.] > The Julia binaries from the website load, but unfortunately don't fully > work. > Why would it "be great to get this working"? Or at least [of interest] for you? I also did wander if it would work but since there is a Windows Julia binary, that we would want to maintain for a long time and not drop support of Julia that way, I do not see this as a priority, or on the horizon. Only that Julia version is supported back to Windows XP. Theoretically using a Linux ELF binary in Windows is interesting, but it could be a long time to a Windows 10-exclusive world(?). >There are also double free or corruption errors with Julia 0.5.0. I don't understand, only in the Windows subsystem, but not same "double free" under Linux with same ELF binary? How can that happen, it's Julia that does the free (and malloc)?! >I tried building Julia 0.4.6 from source and the main issue I hit was that pcre2 requires a stack limit of 16MB, but WSL is limited to 8MB. And ulimit refuses to increase the limit. > I've never understood why there are limits, [such as on file descriptors (except if you want to artificially limit)], except for the fundamental memory limit (and in a sense "CPU time"). I guess the stack is a special case (but could also in theory be unlimitted?). Different cross-platform limits just makes them worse.. [E.g. file descriptors are just memory to the kernel in the end?] > The main problem seems to be the glacially slow filesystem. Also interesting, just on the subsystem that is, otherwise ok? -- Palli.
