Add workaround for building gpgme with musl >= 1.2.4 #181
Conversation
This file contains 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
ueno
approved these changes
Jan 16, 2024
|
@ueno they don't seem to use github but a mailing list, which is a way of communication i've never participated in ;) Thus I've procrastinated on this up to now. Feel free, if you're familiar with the etiquette in mailing lists 😬 🙈 |
|
thank you @jk779!! would be great to get this into a release |
|
thanks for the merge! do you foresee a release coming up? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When trying to compile this with a current alpine linux, the build fails because of an upgrade of musl. musl 1.2.4 removed the LFS64 interfaces, which are used in gpgme. They provide a way to reenable them until sources are updated with
CFLAGS=-D_LARGEFILE64_SOURCE.This adds the workaround to the build config until gpgme updates their code.
Here's a stacktrace of the installation without this patch: https://gist.github.com/jk779/33a16851bbe3c6baf7a024eba1fb7dc3
See #182