Fix linking error #4425
Open
Fix linking error #4425
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
Using fixes described in mapnik#4243 (comment) Fixes mapnik#4243.
Nakaner
force-pushed
the
fix-issue-4243-pr
branch
from
326de80
to
fcdfaeb
Compare
|
rebased onto current master branch |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4425 +/- ##
=======================================
Coverage 74.12% 74.12%
=======================================
Files 493 493
Lines 31845 31845
=======================================
Hits 23605 23605
Misses 8240 8240 ☔ View full report in Codecov by Sentry. |
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.
This pull request uses fixes described in #4243 (comment)
It is an alternative to #4370 but with fewer changes (and addresses the comment by @luk-brue on that pull request.
I can confirm the original bug report on both Arch Linux (same as the reporter) and Ubuntu Jammy.