chkwon / Complementarity.jl

provides a modeling interface for mixed complementarity problems (MCP) and math programs with equilibrium problems (MPEC) via JuMP
Other
75 stars 20 forks source link

Failure to precompile in Julia 1.5: #45

Closed Jovansam closed 3 years ago

Jovansam commented 3 years ago

There is a load error that leads to a failure to precompile in Julia 1.5. See below, at "LoadError: could not load symbol "jl_function_ptr":"

┌ Info: Precompiling Complementarity [a9b2a840-c9d5-5181-a245-8df664c2d6e7]
└ @ Base loading.jl:1278
┌ Warning: Package Complementarity does not have LinearAlgebra in its dependencies:
│ - If you have Complementarity checked out for development and have
│   added LinearAlgebra as a dependency but haven't updated your primary
│   environment's manifest file, try `Pkg.resolve()`.
│ - Otherwise you may need to report an issue with Complementarity
└ Loading LinearAlgebra into Complementarity from project dependency, future warnings for Complementarity are suppressed.
ERROR: LoadError: LoadError: could not load symbol "jl_function_ptr":
The specified procedure could not be found. 
Stacktrace:
[1] PATHSolver.FunctionWrappersQuickFix.FunctionWrapper{Any,Tuple{Any}}(::typeof(identity)) at C:\Users\KitchenComputer\.julia\packages\PATHSolver\tJVDr\src\FunctionWrappersQuickFix.jl:89
[2] top-level scope at C:\Users\KitchenComputer\.julia\packages\PATHSolver\tJVDr\src\FunctionWrappersQuickFix.jl:132
[3] include(::Function, ::Module, ::String) at .\Base.jl:380
[4] include at .\Base.jl:368 [inlined]
[5] include(::String) at C:\Users\KitchenComputer\.julia\packages\PATHSolver\tJVDr\src\PATHSolver.jl:1
[6] top-level scope at C:\Users\KitchenComputer\.julia\packages\PATHSolver\tJVDr\src\PATHSolver.jl:3
[7] include(::Function, ::Module, ::String) at .\Base.jl:380
[8] include(::Module, ::String) at .\Base.jl:368
[9] top-level scope at none:2
[10] eval at .\boot.jl:331 [inlined]
[11] eval(::Expr) at .\client.jl:467
[12] top-level scope at .\none:3
in expression starting at C:\Users\KitchenComputer\.julia\packages\PATHSolver\tJVDr\src\FunctionWrappersQuickFix.jl:132
in expression starting at C:\Users\KitchenComputer\.julia\packages\PATHSolver\tJVDr\src\PATHSolver.jl:3
ERROR: LoadError: Failed to precompile PATHSolver [f5f7c340-0bb3-5c69-969a-41884d311d1b] to C:\Users\KitchenComputer\.julia\compiled\v1.5\PATHSolver\xyGrF_7TF5F.ji.
Stacktrace:
[1] error(::String) at .\error.jl:33
[2] compilecache(::Base.PkgId, ::String) at .\loading.jl:1290
[3] _require(::Base.PkgId) at .\loading.jl:1030
[4] require(::Base.PkgId) at .\loading.jl:928
[5] require(::Module, ::Symbol) at .\loading.jl:923
[6] include(::Function, ::Module, ::String) at .\Base.jl:380
[7] include(::Module, ::String) at .\Base.jl:368
[8] top-level scope at none:2
[9] eval at .\boot.jl:331 [inlined]
[10] eval(::Expr) at .\client.jl:467
[11] top-level scope at .\none:3
in expression starting at C:\Users\KitchenComputer\.julia\packages\Complementarity\jpfgn\src\Complementarity.jl:18
Failed to precompile Complementarity [a9b2a840-c9d5-5181-a245-8df664c2d6e7] to C:\Users\KitchenComputer\.julia\compiled\v1.5\Complementarity\ORstz_7TF5F.ji.

Stacktrace:
[1] error(::String) at .\error.jl:33
[2] compilecache(::Base.PkgId, ::String) at .\loading.jl:1290
[3] _require(::Base.PkgId) at .\loading.jl:1030
[4] require(::Base.PkgId) at .\loading.jl:928
[5] require(::Module, ::Symbol) at .\loading.jl:923
[6] include_string(::Function, ::Module, ::String, ::String) at .\loading.jl:1091
chkwon commented 3 years ago

Thanks for reporting. This seems due to an error in https://github.com/chkwon/PATHSolver.jl/issues/42

Please consider this package: https://github.com/odow/PATH.jl

Eventually, Complementarity.jl will phase out and PATH.jl (not yet officially registered package) will kick in.

Jovansam commented 3 years ago

@chkwon thanks for quick response. PATH.jl is great. Though due to JuMP, at the moment there is a limitation to only linear (and not nonlinear) complementary constraints. So complementarity.jl is a lifesaver in this regard. Thanks for the good work.

chkwon commented 3 years ago

@Jovansam The issue should have been fixed with new version 0.7.2. Please test it and if it doesn't work, please report it back.

Jovansam commented 3 years ago

Tested it out. Works great! Thanks.