diff options
author | James Greenhalgh <james.greenhalgh@arm.com> | 2015-08-25 14:31:11 +0100 |
---|---|---|
committer | Corinna Vinschen <corinna@vinschen.de> | 2015-08-25 16:17:14 +0200 |
commit | 4eca8ea0cf0beb815e57ff1a36a5bfcc74980849 (patch) | |
tree | c07b24fee10387cf5a798fd77b2ac14516415c61 /COPYING.NEWLIB | |
parent | a396499757fdc554a4006b6347016957e1c95cc5 (diff) | |
download | newlib-4eca8ea0cf0beb815e57ff1a36a5bfcc74980849.zip newlib-4eca8ea0cf0beb815e57ff1a36a5bfcc74980849.tar.gz newlib-4eca8ea0cf0beb815e57ff1a36a5bfcc74980849.tar.bz2 |
Always declare "kill" in include/sys/signal.h
Hi,
As I mentioned recently [1], newlib is providing a "kill" symbol to link
against, without declaring "kill" in signal.h. This is confusing for the
libgfortran build, which tries to link against kill (which succeeds), then
tries to use it (which triggers -Werror=implicit-function-declaration).
This patch implements my suggestion in that thread - making the declaration
of 'kill' in libc/include/sys/signal.h unconditional.
I've tested this by building a modified libgfortran on AArch64/ARM to see
that the Werror goes away, and the libgfortran build succeeds.
Is something like this OK for newlib? If so, can someone please commit
it on my behalf, as I have no commit access here.
Otherwise, what is your preferred direction for me to take this patch?
Thanks,
James
Diffstat (limited to 'COPYING.NEWLIB')
0 files changed, 0 insertions, 0 deletions