Skip to content
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

precompile error on Windows #58

Open
PatMcFarlane opened this issue Feb 4, 2025 · 1 comment
Open

precompile error on Windows #58

PatMcFarlane opened this issue Feb 4, 2025 · 1 comment

Comments

@PatMcFarlane
Copy link

PatMcFarlane commented Feb 4, 2025

I'm having trouble using MKLSparse on a Windows 11 machine. I get an error when precompiling:

ERROR: The following 1 direct dependency failed to precompile:

MKLSparse

Failed to precompile MKLSparse [0c723cd3-b8cd-5d40-b370-ba682dde9aae] to "C:\\Users\\pmcfarla\\.julia\\compiled\\v1.11\\MKLSparse\\jl_9252.tmp".
ERROR: LoadError: too many parameters for type AbstractTriangular
Stacktrace:
 [1] top-level scope
   @ C:\Users\pmcfarla\.julia\packages\MKLSparse\aP1wu\src\interface.jl:17
 [2] include(mod::Module, _path::String)
   @ Base .\Base.jl:558
 [3] include(x::String)
   @ MKLSparse C:\Users\pmcfarla\.julia\packages\MKLSparse\aP1wu\src\MKLSparse.jl:1
 [4] top-level scope
   @ C:\Users\pmcfarla\.julia\packages\MKLSparse\aP1wu\src\MKLSparse.jl:61
 [5] include
   @ .\Base.jl:558 [inlined]
 [6] include_package_for_output(pkg::Base.PkgId, input::String, depot_path::Vector{String}, dl_load_path::Vector{String}, load_path::Vector{String}, concrete_deps::Vector{Pair{Base.PkgId, UInt128}}, source::Nothing)
   @ Base .\loading.jl:2721
 [7] top-level scope
   @ stdin:4
in expression starting at C:\Users\pmcfarla\.julia\packages\MKLSparse\aP1wu\src\interface.jl:10
in expression starting at C:\Users\pmcfarla\.julia\packages\MKLSparse\aP1wu\src\MKLSparse.jl:1
in expression starting at stdin:

I'm really not very savvy about these things. Grateful for any assistance.

-Patrick

@PatMcFarlane
Copy link
Author

PatMcFarlane commented Feb 21, 2025

I think the problem is that in interface.jl:10, one needs to replace VERSION>=v"1.11" with VERSION>=v"1.11-"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant