[6.40] [openssl] builtin: destination of include files was not correct#22074
Open
root-project-bot wants to merge 1 commit intoroot-project:v6-40-00-patchesfrom
Open
[6.40] [openssl] builtin: destination of include files was not correct#22074root-project-bot wants to merge 1 commit intoroot-project:v6-40-00-patchesfrom
root-project-bot wants to merge 1 commit intoroot-project:v6-40-00-patchesfrom
Conversation
Compilation with builtin_openssl probably just worked fine because it picked system-wide openssl headers rather than the builtin ones. Found out while investigating failures in root-project#21947 (cherry picked from commit 967a2f2)
Test Results 22 files 22 suites 3d 10h 4m 18s ⏱️ For more details on these failures, see this check. Results for commit 6942976. |
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.
Backport of #22026, requested by @dpiparo. For your information @ferdymercury