libssh: Unbreak build with declarations after statement #14821
Merged
Conversation
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
|
Jakuje has previously contributed to projects/libssh. The previous PR was #14734 |
in generated code Signed-off-by: Jakub Jelen <jjelen@redhat.com>
Jakuje
force-pushed
the
declaration-after-statement
branch
from
2fded5c to
156deb3
Compare
DavidKorczynski
approved these changes
Jan 22, 2026
ranok
pushed a commit
to ranok/oss-fuzz
that referenced
this pull request
Jan 22, 2026
in generated code Recent changes in libssh introduced some generated code that violates the `declaration-after-statement` requirement and that is breaking today's build. This is an attempt to fix it Signed-off-by: Jakub Jelen <jjelen@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
in generated code
Recent changes in libssh introduced some generated code that violates the
declaration-after-statementrequirement and that is breaking today's build. This is an attempt to fix it