-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong v0.2.2? #10
Comments
It was on purpose because there was major breakage. Precompilation isn't enabled but it's not disabled. I'll get this fixed but it shouldn't be causing any major problems? Right? If a library depends on this and precompiles, it would just precompile it. |
I got this kind of error:
When doing a fresh install of the DiffEq-system on Julia 0.6. |
BTW, similarly for
My understanding is that a package needs to opt-into pre-compilation. As not all of them are safe to be pre-compiled. |
That understanding is wrong. That has nothing to do with lack of precompile statements. It's due to broken precompile caches. One thing that can cause it is the Iterators and FFTW naming in Base. If you have Distributions anywhere in the chain you'll hit this issue. JuliaStats/Distributions.jl#631 Another thing that can cause it is attempting to recompile when the same session is open. It's a v0.6 bug and I don't think it has been reported yet. But precompiling a library which has dependents that don't explicitly say |
Unless they changed it in v0.7? |
Ha, I was still in 0.4: https://docs.julialang.org/en/release-0.4/manual/modules/#module-initialization-and-precompilation on that one... Ok, I was aware of the Iterators.jl issue but not that FFTW is also affected. I'll read up and maybe report back. |
Doing JuliaStats/Distributions.jl#631 (comment) seems to fix it. |
Tag v0.2.2 points to the same commit as v0.1.0. If that is indeed intended then it causes problems as there is no pre-compilation enabled in 0.1.0.
The text was updated successfully, but these errors were encountered: