Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specify missing void parameter in function declarators #302

Merged
merged 2 commits into from
Oct 29, 2023

Conversation

chrstphrchvz
Copy link
Contributor

@chrstphrchvz
Copy link
Contributor Author

See #301 (comment) regarding CI failure.

Copy link
Member

@raimue raimue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. But I did not try to confirm whether this caught all warnings of this kind.

@chrstphrchvz
Copy link
Contributor Author

Looks good to me. But I did not try to confirm whether this caught all warnings of this kind.

Currently, this PR does not address all -Wstrict-prototypes warnings. It only tries to deal with any which MacPorts itself would be responsible for. There are plenty more in vendor (Tcl, etc.) and autoconf tests; should this PR instead deal with those as well?

Also, this would only resolves warnings seen in make all and the macOS 13 build log the ticket referred to; I have not combed through the code to see if that missed any others (e.g. not compiled or hidden from the compiler).

@chrstphrchvz
Copy link
Contributor Author

chrstphrchvz commented Oct 29, 2023

Added fix for the one -Wstrict-prototypes warning seen during the Tcl 8.6.13 build. It has been accepted by upstream for Tcl 8.6.14.

@raimue
Copy link
Member

raimue commented Oct 29, 2023

Currently, this PR does not address all -Wstrict-prototypes warnings. It only tries to deal with any which MacPorts itself would be responsible for. There are plenty more in vendor (Tcl, etc.) and autoconf tests; should this PR instead deal with those as well?

I agree if we need it, we should try to submit this upstream if they did not already address this. Then sync it with a new upstream version. Just as you did now. 😃

Our patches to the vendored sources should be kept minimal and only apply build fixes we absolutely need. And vendored code throws other warnings as well.

@raimue raimue merged commit 4fdb948 into macports:master Oct 29, 2023
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants