ext: systems missing libiconv will see a relevant error message #2505
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
instead of a syntax error from extconf.rb Fixes #2487
|
Note that this was originally broken in 8de0526 / v1.11.0 |
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.
What problem is this PR intended to solve?
Fixes #2487
systems missing libiconv will see a relevant error message instead of a syntax error from extconf.rb
Have you included adequate test coverage?
I have only reproduced the issue on OpenBSD systems, for which we do not have test coverage today. If someone familiar with OpenBSD and Github Actions would like to submit a PR to do so, I would consider it.
Does this change affect the behavior of either the C or the Java implementations?
No behavioral changes.