-
Notifications
You must be signed in to change notification settings - Fork 66
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
Segfault from jll
package: Assertion `(((jl_datatype_t*)(dt))->layout->nfields) == 1' failed
#395
Comments
I think the problem is indeed with the build script, packages based on libcxxwrap_julia need to be built against specific versions of libjulia, probably here you are loading a JLL that was compiled for a different Julia version than the one you are running (I don't know which one it picks by default). You can check an example here: /~https://github.com/JuliaPackaging/Yggdrasil/blob/master/L/libsingular_julia/build_tarballs.jl Use of the |
Thank you for the tip! I can confirm that after changing the platform variable to
the If I do
then the |
This is followup to #394, which is now failing at a different stage due to upgrading
CxxWrap.jl
andlibcxxwrap_julia_jll.jl
(now their versions are v0.14.2 and v0.11.0 respective)The problem
I wrote a Julia wrapper for the ghostbasil C++ library, and it works fine with a local installation of
CxxWrap.jl
andlibcxxwrap_julia_jll.jl
.However, when I tried to make a
jll
package for this wrapper, thejll
package can be loaded but segfaults when I try to run things, even though it built successfully (tested on x86_64-linux-gnu).Do you have any insights/suggestions? It is mysterious to me that the wrapper code works locally, but not within a
jll
package. The error message is not very meaningful to me:MWE:
Possible reason: incorrect
build_tarballs.jl
I am new to BinaryBuilder.jl, so perhaps my
build_tarballs.jl
is problematic? However it seems to build successfully, so I feel it is not the problemAgain, any insights or suggestions would be highly appreciated. Thank you very much for your time.
The text was updated successfully, but these errors were encountered: