From: Michael Dorin <bsd_mike@yahoo.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] include_next problem
Date: Thu, 28 Jun 2007 15:23:00 -0000 [thread overview]
Message-ID: <962219.67937.qm@web38210.mail.mud.yahoo.com> (raw)
Hello,
I am trying to build an ecos application which
includes stddef. I get the error below:
../../../src/ecos/include/stddef.h" includes itself
#include_next <stddef.h>
#include_next is on the bottom of stddef.h.
Simply removing the include_next seems to be a bad
thing too.
I am using the arm.com c compiler.
Any ideas on how to fix this?
-Mike
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2007-06-28 13:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 15:23 Michael Dorin [this message]
2007-06-28 15:29 ` Andrew Lunn
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=962219.67937.qm@web38210.mail.mud.yahoo.com \
--to=bsd_mike@yahoo.com \
--cc=dorin@gr-303.com \
--cc=ecos-discuss@sources.redhat.com \
/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).