From: Andrew Lunn <andrew@lunn.ch>
To: Ellen <zh.yi.99@gmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] How to enable POSIX message queue in eCos environment?
Date: Wed, 29 Jun 2005 20:08:00 -0000 [thread overview]
Message-ID: <20050629200807.GF8479@lunn.ch> (raw)
In-Reply-To: <89a6346f05062912554dee1fb9@mail.gmail.com>
On Wed, Jun 29, 2005 at 02:55:40PM -0500, Ellen wrote:
> Hi all,
>
> I'm new to eCos and trying to run on Linux synthetic target. Have a
> question here for using POSIX message queue in eCos.
>
> I noticed in the reference manual, it is mentioned that "The presence
> of message queues is controlled by the CYGPKG_POSIX_MQUEUES option.
> Setting this option will cause _POSIX_MESSAGE_PASSING to be defined
> and the message queue API to be make available." In my case, I
> checked the ecos.ecc and pkgconf/isoinfra.h, I have the option
> CYGINT_ISO_MQUEUE (instead of CYGPKG_POSIX_MQUEUES) set to 0, which
> consequently makes the _POSIX_MESSAGE_PASSING undefined. So when
> compiling, I got the error of undeclared "O_CREAT" and implicit
> declaration of "mq_open".
>
> Since the CYGINT_ISO_MQUEUE is automatically defined in configtool, I
> went back to the configuration tool, try to set this option.
> Unfortunately, I found that under the "POSIX message queues", the
> "maximum number of open message queues" is grey and its value is 0.
>
> Anybody can help to set this mqueue option and make the message queue
> API available?
Use the posix template.
Andrew
--
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 prev parent reply other threads:[~2005-06-29 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 19:55 Ellen
2005-06-29 20:08 ` Andrew Lunn [this message]
2005-06-29 23:44 ` Ellen
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=20050629200807.GF8479@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=zh.yi.99@gmail.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).