using JuMP - LoadError: UndefVarError: start not defined

Hello,

I’ve just installed julia 1.0.0. When running “using JuMP” I get the following error:
[ Info: Precompiling JuMP [4076af6c-e467-56ae-b986-b466b2749572]
ERROR: LoadError: LoadError: UndefVarError: start not defined
Stacktrace:
[1] getproperty(::Module, ::Symbol) at ./sysimg.jl:13
[2] top-level scope at none:0
[3] include at ./boot.jl:317 [inlined]
[4] include_relative(::Module, ::String) at ./loading.jl:1038
[5] include at ./sysimg.jl:29 [inlined]
[6] include(::String) at /home/stefano/.julia/packages/ForwardDiff/2v3a4/src/ForwardDiff.jl:3
[7] top-level scope at none:0
[8] include at ./boot.jl:317 [inlined]
[9] include_relative(::Module, ::String) at ./loading.jl:1038
[10] include(::Module, ::String) at ./sysimg.jl:29
[11] top-level scope at none:2
[12] eval at ./boot.jl:319 [inlined]
[13] eval(::Expr) at ./client.jl:389
[14] top-level scope at ./none:3
in expression starting at /home/stefano/.julia/packages/ForwardDiff/2v3a4/src/partials.jl:25
in expression starting at /home/stefano/.julia/packages/ForwardDiff/2v3a4/src/ForwardDiff.jl:16
ERROR: LoadError: Failed to precompile ForwardDiff [f6369f11-7733-5829-9624-2563aa707210] to /home/stefano/.julia/compiled/v1.0/ForwardDiff/k0ETY.ji.
Stacktrace:
[1] error(::String) at ./error.jl:33
[2] macro expansion at ./logging.jl:313 [inlined]
[3] compilecache(::Base.PkgId, ::String) at ./loading.jl:1184
[4] _require(::Base.PkgId) at ./logging.jl:311
[5] require(::Base.PkgId) at ./loading.jl:852
[6] macro expansion at ./logging.jl:311 [inlined]
[7] require(::Module, ::Symbol) at ./loading.jl:834
[8] include at ./boot.jl:317 [inlined]
[9] include_relative(::Module, ::String) at ./loading.jl:1038
[10] include(::Module, ::String) at ./sysimg.jl:29
[11] top-level scope at none:2
[12] eval at ./boot.jl:319 [inlined]
[13] eval(::Expr) at ./client.jl:389
[14] top-level scope at ./none:3
in expression starting at /home/stefano/.julia/packages/ReverseDiffSparse/bP6lF/src/ReverseDiffSparse.jl:4
ERROR: LoadError: Failed to precompile ReverseDiffSparse [89212889-6d3f-5f97-b412-7825138f6c9c] to /home/stefano/.julia/compiled/v1.0/ReverseDiffSparse/VqGhr.ji.
Stacktrace:
[1] error(::String) at ./error.jl:33
[2] macro expansion at ./logging.jl:313 [inlined]
[3] compilecache(::Base.PkgId, ::String) at ./loading.jl:1184
[4] _require(::Base.PkgId) at ./logging.jl:311
[5] require(::Base.PkgId) at ./loading.jl:852
[6] macro expansion at ./logging.jl:311 [inlined]
[7] require(::Module, ::Symbol) at ./loading.jl:834
[8] include at ./boot.jl:317 [inlined]
[9] include_relative(::Module, ::String) at ./loading.jl:1038
[10] include(::Module, ::String) at ./sysimg.jl:29
[11] top-level scope at none:2
[12] eval at ./boot.jl:319 [inlined]
[13] eval(::Expr) at ./client.jl:389
[14] top-level scope at ./none:3
in expression starting at /home/stefano/.julia/packages/JuMP/6aWuF/src/JuMP.jl:20
ERROR: Failed to precompile JuMP [4076af6c-e467-56ae-b986-b466b2749572] to /home/stefano/.julia/compiled/v1.0/JuMP/DmXqY.ji.
Stacktrace:
[1] error(::String) at ./error.jl:33
[2] macro expansion at ./logging.jl:313 [inlined]
[3] compilecache(::Base.PkgId, ::String) at ./loading.jl:1184
[4] _require(::Base.PkgId) at ./logging.jl:311
[5] require(::Base.PkgId) at ./loading.jl:852
[6] macro expansion at ./logging.jl:311 [inlined]
[7] require(::Module, ::Symbol) at ./loading.jl:834

Any idea?

Please see this announcement regarding the status of JuMP on 1.0.

The development version of JuMP is working on 1.0, so if you are feeling adventurous you can try using dev JuMP. Be advised however, that it is very much still in development.

In some other good news, I am very nearly done getting JuMP 0.18 to run on 1.0, so you should have it fairly soon. If you want to track the status see this PR.

1 Like

Hello, thank you for the answer.
I’m not sure how to actually select dev JuMP.

You can just do ]dev JuMP in the REPL.

Before experimenting with that I’d recommend familiarizing yourself with the Pkg documentation a bit.

If you are looking for a stable, usable linear or quadratic programming interface on 1.0, you’ll just have to wait a bit, though hopefully it won’t be too long now.

If you are working on non-linear programs I also recommend checking out Optim.jl which is now fully 1.0 ready.