public inbox for newlib-cvs@sourceware.org help / color / mirror / Atom feed
From: Sebastian Huber <sh@sourceware.org> To: newlib-cvs@sourceware.org Subject: [newlib-cygwin] RTEMS: Declare ioctl() also if _KERNEL is defined Date: Fri, 8 Jul 2022 04:58:58 +0000 (GMT) [thread overview] Message-ID: <20220708045858.F043C3858C2C@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=4ab39e0a85a0fa9ddab6a179040b24dbfabd87ad commit 4ab39e0a85a0fa9ddab6a179040b24dbfabd87ad Author: Sebastian Huber <sebastian.huber@embedded-brains.de> Date: Wed Jul 6 16:42:28 2022 +0200 RTEMS: Declare ioctl() also if _KERNEL is defined This fixes the following warning in libbsd: rtems/blkdev.h:200:10: warning: implicit declaration of function 'ioctl'; did you mean 'ifioctl'? [-Wimplicit-function-declaration] Remove unnecessary includes. Diff: --- newlib/libc/sys/rtems/include/sys/ioccom.h | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/newlib/libc/sys/rtems/include/sys/ioccom.h b/newlib/libc/sys/rtems/include/sys/ioccom.h index 2a8416c41..1044a27e9 100644 --- a/newlib/libc/sys/rtems/include/sys/ioccom.h +++ b/newlib/libc/sys/rtems/include/sys/ioccom.h @@ -36,7 +36,6 @@ #define _SYS_IOCCOM_H_ #include <sys/types.h> -#include <stdint.h> typedef unsigned long ioctl_command_t; @@ -80,14 +79,10 @@ typedef unsigned long ioctl_command_t; #define IOCPARM_IVAL(x) ((int)(intptr_t)(void *)*(caddr_t *)(void *)(x)) #endif -#else - -#include <sys/cdefs.h> +#endif __BEGIN_DECLS int ioctl(int, ioctl_command_t, ...); __END_DECLS -#endif - #endif /* !_SYS_IOCCOM_H_ */
reply other threads:[~2022-07-08 4:58 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20220708045858.F043C3858C2C@sourceware.org \ --to=sh@sourceware.org \ --cc=newlib-cvs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).