From: Birahim Larou Fall <BLFall@scmmicro.fr>
To: eCos Disuss <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Possible omission in Lwip?
Date: Mon, 03 Apr 2006 12:18:00 -0000 [thread overview]
Message-ID: <OFFB9CF3EB.C1B6DD1E-ONC1257145.00424FBB-C1257145.0043CE06@scmmicro.fr> (raw)
In-Reply-To: <20060328204719.GZ3228@lunn.ch>
In file eCos\packages\net\lwip_tcpip\current\include\lwip, struct
timeval is defined if LWIP_TIMEVAL_PRIVATE is defined, but function
lwip_select() use struct timeval as an argument and it's declared in
sockets.h with or without LWIP_TIMEVAL_PRIVATE defined. Of course LWIP
compile witout any error because each time that sockets is included,
LWIP_TIMEVAL_PRIVATE is first defined.
/*
* only define this in api_sockets_wrapper.c so it does not interfere
* with other projects namespaces where timeval is present
*/
#ifdef LWIP_TIMEVAL_PRIVATE
struct timeval {
long tv_sec; /* seconds */
long tv_usec; /* and microseconds */
};
#endif
int lwip_select(int maxfdp1, fd_set *readset, fd_set *writeset, fd_set
*exceptset,
struct timeval *timeout);
Fall Birahim
Digital TV Firmware Engineer
Elsys Design for SCM Microsystems
--
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:[~2006-04-03 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 23:44 [ECOS] Re: Fail booting from P30 Andrew Lunn
2006-04-03 12:18 ` Birahim Larou Fall [this message]
2006-04-09 11:41 ` [ECOS] Possible omission in Lwip? Andrew Lunn
2006-04-10 15:35 ` Birahim Larou Fall
2006-04-10 17:54 ` 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=OFFB9CF3EB.C1B6DD1E-ONC1257145.00424FBB-C1257145.0043CE06@scmmicro.fr \
--to=blfall@scmmicro.fr \
--cc=ecos-discuss@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).