From: David Fernandez <david.fernandez.work@googlemail.com>
To: eCos development list <ecos-devel@ecos.sourceware.org>
Subject: I have a few patches to fix minor things that I would like to have applied.
Date: Wed, 21 Aug 2013 11:39:00 -0000 [thread overview]
Message-ID: <CAA6dH318vYJZnZ1zyGCy6WO1rKKc8r+FNMEY5M-WuHpZm8przg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 485 bytes --]
Hi there,
If any repository administrator is listening in this holiday period...
First one is to avoid warnings for those pedantic people that like to
compile everything with -pedantic...
Is quite simple, and avoids a big row with evryone that has an opinion
on the lots of bugs prevented by having errors about old half-way
specified ANSI C89 (or is it C80...) stuff.
Let me know if that is ok.
I have a few others more meaningful, but I guess I start with easy stuff.
Regards.
[-- Attachment #2: ecos-pedantic.patch --]
[-- Type: application/octet-stream, Size: 2194 bytes --]
Index: packages/isoinfra/current/include/float.h
===================================================================
RCS file: /cvs/ecos/ecos/packages/isoinfra/current/include/float.h,v
retrieving revision 1.4
diff -u -r1.4 float.h
--- packages/isoinfra/current/include/float.h 29 Jan 2009 17:49:50 -0000 1.4
+++ packages/isoinfra/current/include/float.h 21 Aug 2013 11:01:00 -0000
@@ -61,6 +61,7 @@
//======================================================================
*/
+__extension__
#include_next <float.h>
/* EOF float.h */
Index: packages/isoinfra/current/include/limits.h
===================================================================
RCS file: /cvs/ecos/ecos/packages/isoinfra/current/include/limits.h,v
retrieving revision 1.8
diff -u -r1.8 limits.h
--- packages/isoinfra/current/include/limits.h 13 May 2009 08:21:35 -0000 1.8
+++ packages/isoinfra/current/include/limits.h 21 Aug 2013 11:01:00 -0000
@@ -218,6 +218,7 @@
/* Secondly only include if we haven't already been included by it. */
#ifndef _GCC_LIMITS_H_
+__extension__
# include_next <limits.h>
#endif
Index: packages/isoinfra/current/include/stdarg.h
===================================================================
RCS file: /cvs/ecos/ecos/packages/isoinfra/current/include/stdarg.h,v
retrieving revision 1.4
diff -u -r1.4 stdarg.h
--- packages/isoinfra/current/include/stdarg.h 29 Jan 2009 17:49:50 -0000 1.4
+++ packages/isoinfra/current/include/stdarg.h 21 Aug 2013 11:01:00 -0000
@@ -61,6 +61,7 @@
//======================================================================
*/
+__extension__
#include_next <stdarg.h>
/* EOF stdarg.h */
Index: packages/isoinfra/current/include/stddef.h
===================================================================
RCS file: /cvs/ecos/ecos/packages/isoinfra/current/include/stddef.h,v
retrieving revision 1.5
diff -u -r1.5 stddef.h
--- packages/isoinfra/current/include/stddef.h 29 Jan 2009 17:49:50 -0000 1.5
+++ packages/isoinfra/current/include/stddef.h 21 Aug 2013 11:01:00 -0000
@@ -60,6 +60,7 @@
//======================================================================
*/
+__extension__
#include_next <stddef.h>
/* EOF stddef.h */
next reply other threads:[~2013-08-21 11:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 11:39 David Fernandez [this message]
2013-08-21 11:55 ` David Fernandez
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=CAA6dH318vYJZnZ1zyGCy6WO1rKKc8r+FNMEY5M-WuHpZm8przg@mail.gmail.com \
--to=david.fernandez.work@googlemail.com \
--cc=ecos-devel@ecos.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: link
Be 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).