Add void to function declarations for EVP_EncryptInit check #542
+2
−2
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
gcc 11.1.1 complains about not having strict function prototypes (-Wstrict-prototypes) when attempting to test for linkage with openssl. This warning was added in PR cisco#284. Why it started acting up now is unknown. It may be that gcc 11.1.1 have changed how and when they emit this warning. Adding void to the function declarations seems to silence this warning and allow the test to run to completion.
paulej
approved these changes
Jun 9, 2021
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.
gcc 11.1.1 complains about not having strict function prototypes
(-Wstrict-prototypes) when attempting to test for linkage with openssl.
This warning was added in PR #284. Why it started acting up now is
unknown. It may be that gcc 11.1.1 have changed how and when they emit
this warning.
Adding void to the function declarations seems to silence this warning
and allow the test to run to completion.