From: "Picque Sébastien" <S.Picque@TELEVIC.com>
To: <ecos-discuss@sourceware.org>
Subject: [ECOS] About posix compatibility with some macro on time.h
Date: Wed, 25 Apr 2007 08:58:00 -0000 [thread overview]
Message-ID: <A231E60AABF3F143B244E70FB6A3B65540AF2A@nt-email.TELEVIC.COM> (raw)
Hi all,
I am surprised to see that the header file from posix compatibilty are not matching with the file coming from Linux standart.
For example some definitions are missing ( ITIMER_REAL.)
Is it a normal behaviour ?
Thank you for your help and support
Regards,
Sebastien Picque
**********************************************************************
Embedded Software Engineer Consultant (Company Alten).
Phone number: + 32 (0)51 30 30 45 (poste 283).
*********************************************************************
--
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-04-25 8:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 8:58 Picque Sébastien [this message]
2007-04-25 9:49 ` 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=A231E60AABF3F143B244E70FB6A3B65540AF2A@nt-email.TELEVIC.COM \
--to=s.picque@televic.com \
--cc=ecos-discuss@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).