-
Notifications
You must be signed in to change notification settings - Fork 81
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
Build problems with julia 0.5.0 - dev #193
Comments
btw; i can now confim on my own box:
|
Hi Andreas, The line ERROR: Base.Pkg.PkgError("Compose.jl is not an installed package") Suggests something else. Did you mean: julia> Pkg.build("Compose") without the .jl suffix ? /tm From: Andreas Lobinger [mailto:notifications@github.com] btw; i can now confim on my own box: _ _ ()_ | A fresh approach to technical computing julia> Pkg.build("Compose.jl") signal (15): Terminated julia> — |
@ethomag I think you are right, this might be anthor 0.5 problem. However for your/our problem i think the https://github.com/JuliaLang/julia/blob/master/HISTORY.md "Language Changes" Tuple change applies. |
Looks like more complicated, the makeform macro tries some local optimization... |
No, I don't think this is necessarily complicated. If the original author just has a look at it, it is probably obvious to hum/her. It looks like the "in" expession ast has changed or an extra layer of tuples is added or something in that area. I am not fluent enough in julia at this level. Sent from my Android phone using TouchDown (www.nitrodesk.com) -----Original Message----- Looks like more complicated, the makeform macro tries some local optimization... — |
SImply because JuliaLang/julia#15524 ? |
@ScottPJones fix makes Compose build again. Thanks! |
Fix #193, issue with makeform macro in v0.5
I'm trying to build Gadfly, using the julia 0.5.0 dev (master). But I get som problems with Compose.jl, I think:
Looking at line 188 in my Compse/src/form.jl, I see:
In which I guess the ERROR: LoadError: LoadError: Not an 'in' expression origins from.
The text was updated successfully, but these errors were encountered: