Fix warnings from kill and getpid not being implemented #183
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.
Summary of changes
Versions of GCC which supply newer Newlib versions (unsure of the exact Newlib version, I think it's the one included with GCC 11 and newer) now appear to want the _getpid() and _kill() functions defined. I checked using radare, and it appears they get pulled in as dependencies of the C++ standard library, which has been built with exception handling enabled and therefore calls things like abort(). So, these warnings will show up whenever someone links an application which uses STL features.
In the long term the best solution is to rebuild the STL with exceptions disabled, or switch to a toolchain which has that done for us, but in the meantime this will stop the warnings from bothering people.
Impact of changes
None
Migration actions required
None
Documentation
None
Pull request type
Test results
Reviewers