Skip to content

fix #459: Set __STRICT_ANSI__=1 for non-gnu standards #460

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
Jul 7, 2025
Merged

fix #459: Set __STRICT_ANSI__=1 for non-gnu standards #460

merged 2 commits into from
Jul 7, 2025

Conversation

ludviggunne
Copy link
Contributor

No description provided.

@ludviggunne
Copy link
Contributor Author

@firewave does this look OK to you?

@danmar danmar merged commit c7e9974 into danmar:master Jul 7, 2025
16 checks passed
@ludviggunne ludviggunne deleted the 459 branch July 7, 2025 08:48
@firewave
Copy link
Collaborator

firewave commented Jul 7, 2025

@firewave does this look OK to you?

Looks like it. I had not replied yet because I wanted to think about the awkwardness in the handling but I think that should go away when the defined are being re-done - see #386 and #387.

danmar pushed a commit that referenced this pull request Jul 11, 2025
@ludviggunne @danmar
fix #459: Set __STRICT_ANSI__=1 for non-gnu standards (#460)
4d9a930
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@ludviggunne @firewave @danmar