upgrade dependency github.com/ebitengine/purego to avoid regression#514
Merged
ClaytonNorthey92 merged 1 commit intomainfrom May 22, 2025
Merged
Conversation
with go toolchains 1.24.3 or 1.23.9, github.com/ebitengine/purego v0.8.2 will fail to build with the following error: ``` link: duplicated definition of symbol dlopen, from github.com/ebitengine/purego and github.com/ebitengine/purego ``` this can be avoided by upgrading the dependency to v0.8.3. do so. fixes #513
ClaytonNorthey92
requested review from
AL-CT,
jcvernaleo,
marcopeereboom and
max-sanchez
max-sanchez
approved these changes
May 22, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
with go toolchains 1.24.3 or 1.23.9, github.com/ebitengine/purego v0.8.2 will fail to build with the following error:
fixes #513
Changes
this can be avoided by upgrading the dependency to v0.8.3. do so.