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

link separate binaries for JuliaInterface for separate Julia versions #691

Closed
fingolfin opened this issue Sep 9, 2021 · 2 comments
Closed

Comments

@fingolfin
Copy link
Member

fingolfin commented Sep 9, 2021

Right now, if one uses the same GAP.jl version in multiple Julia versions on one computer, this can lead to crashes because all those Julia versions will end up sharing the same .julia/packages/GAP/??????/pkg/JuliaInterface/bin/x86_64-apple-darwin14-julia64-kv8/JuliaInterface.so loadable module; but that .so file actually strongly depends on the Julia version it was linked against.

One way to fix this would be to extend the GAP arch string yet again, and insert the Julia version (at least the major.minor part, or perhaps just the minor part into it. So e.g. x86_64-apple-darwin14-julia64-kv8 would perhaps becomes x86_64-apple-darwin14-julia1.6-64-kv8

Another way to resolve it would be to have a JuliaInterface JLL, see #619

@ThomasBreuer
Copy link
Member

I think this problem occurs not only for JuliaInterface but also for other GAP packages.

@fingolfin
Copy link
Member Author

This should be resolved in GAP.jl 0.8.0, where the GAPARCH now indeed contains the Julia version, e.g. aarch64-apple-darwin20-julia64-kv8-1.8 or x86_64-apple-darwin14-julia64-kv8-1.7

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

2 participants