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

Bump GMT to 6.4.0 #36

Merged
merged 2 commits into from
Jun 20, 2022
Merged

Bump GMT to 6.4.0 #36

merged 2 commits into from
Jun 20, 2022

Conversation

maxrjones
Copy link
Member

No description provided.

@seisman
Copy link
Member

seisman commented Jun 19, 2022

Also need to update the GMT version information in README.

@maxrjones
Copy link
Member Author

Not sure if I should ignore the validator failure for the Julia components

@PaulWessel
Copy link
Member

Not sure if I should ignore the validator failure for the Julia components

Not sure what that means - probably @joa-quim territory?

@joa-quim
Copy link
Member

joa-quim commented Jun 20, 2022

Not our fault and really nothing we (I) can do for now.
The problem is that Unix once again played its favorite game: breaking dependencies.

On *nix, when no GMT if found, GMT.jl automatically installs one via Conda. But Conda decided to start use the shiny shiny new GCC12 that has a new libstdc++ incompatible with predecessors. So those GMT builds cannot be used with current Julia(s) because of that. Add to it that they (the master Julians) have not been able to cross compile libraries from GCC 12.

See what Windows users are safe from because we use the obvious MSVC framework to build our binaries?

Failed to precompile GMT [5752ebe1-31b9-557e-87aa-f909b540aa54] to /srv/julia/pkg/compiled/v1.7/GMT/jl_gIdOKB.
ERROR: LoadError: could not load library "/srv/conda/envs/notebook/lib/libgmt.so"
/srv/julia/bin/../lib/julia/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /srv/conda/envs/notebook/lib/./libgdal.so.31)

@maxrjones
Copy link
Member Author

Thanks for the explanation. Merging since the problem exists for both 6.3 and 6.4 and as Joaquim said, there's nothing we can do.

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

Successfully merging this pull request may close these issues.

4 participants