It doesn't, at least for me. ZMQ tests still segfault. -- mb
On Thu, Jun 25, 2015 at 5:36 PM, Tony Kelman <t...@kelman.net> wrote: > 0.3.10 (released yesterday) should fix this error. > > > On Thursday, June 25, 2015 at 10:02:09 AM UTC-4, Miguel Bazdresch wrote: >> >> These issues may be relevant: >> >> https://github.com/JuliaLang/ZMQ.jl/issues/83 >> >> https://github.com/JuliaLang/IJulia.jl/issues/323 >> >> >> -- mb >> >> On Thu, Jun 25, 2015 at 9:37 AM, Grigoriy Isaev <grigoriy...@gmail.com> >> wrote: >> >>> It seems that there is unfixed bug somewhere in Juno distribution. >>> Latest 64 bit Juno is version 0.3.7 and it has this bug. If i install >>> latest Julia 0.4.0 - zero MQ builds correctly and everything is fine with >>> Ijulia notebooks using 0.4.0 version >>> >>> >>> >>> четверг, 25 июня 2015 г., 16:32:33 UTC+3 пользователь Grigoriy Isaev >>> написал: >>> >>>> Hi! I am trying to set up Ijulia. I've cleand my PC from all previuos >>>> versions of Julia/Ipython and installed fresh 64 bit Anaconda 3 python >>>> distribution + downloaded Juno 64 bit. >>>> >>>> After i launch Ipython i can see Ijulia option, but trying to create >>>> notebooks i get "kernell has died" message and a ZMQ error reference. >>>> >>>> I can not re-build ZMQ on my PC, i get the following errors: >>>> >>>> =================================[ ERROR: ZMQ >>>> ]================================= >>>> >>>> Provider PackageManager failed to satisfy dependency zmq >>>> while loading C:\Users\Gisaev\.julia\v0.3\ZMQ\deps\build.jl, in >>>> expression starting on line 23 >>>> >>>> ================================[ BUILD ERRORS >>>> ]================================ >>>> >>>> WARNING: ZMQ had build errors. >>>> >>>> - packages with build errors remain installed in >>>> C:\Users\Gisaev\.julia\v0.3 >>>> - build the package(s) and all dependencies with `Pkg.build("ZMQ")` >>>> - build a single package by running its `deps/build.jl` script >>>> >>>> >>>> I tried Pkg.checkout on both ZMQ and Ijulia but to no avail. Ipython >>>> notebooks work just fine. >>>> >>>> Any thoughts on what might be the problem? >>>> >>> >>
