From: Andrew Lunn <andrew@lunn.ch>
To: Birahim Larou Fall <BLFall@scmmicro.fr>
Cc: eCos Disuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Possible omission in Lwip?
Date: Mon, 10 Apr 2006 17:54:00 -0000 [thread overview]
Message-ID: <20060410175416.GB8017@lunn.ch> (raw)
In-Reply-To: <OFB8272DBA.16381AC9-ONC125714C.0054EA7D-C125714C.0055F36D@scmmicro.fr>
On Mon, Apr 10, 2006 at 05:30:39PM +0200, Birahim Larou Fall wrote:
> The problem, Mr Andrew, is that I include
> eCos\packages\net\lwip_tcpip\current\include\lwip in my source file
That is a directory, not a file, so you cannot #include it.
It looks like you should be including
<lwip/network.h>
> and I
> don't want to define LWIP_TIMEVAL_PRIVATE (because I don't use TIMEVAL) so
> IT generates an error.
This also does not look right either
lunn@londo:~/eCos/anoncvs-clean/packages/net/lwip_tcpip/current/include$ grep -n -r LWIP_TIMEVAL_PRI *
lwip/sockets.h:212:#ifndef LWIP_TIMEVAL_PRIVATE
lwip/sockets.h:213:#define LWIP_TIMEVAL_PRIVATE 1
lwip/sockets.h:216:#if LWIP_TIMEVAL_PRIVATE
212:#ifndef LWIP_TIMEVAL_PRIVATE
213:#define LWIP_TIMEVAL_PRIVATE 1
214:#endif
215:
216:#if LWIP_TIMEVAL_PRIVATE
struct timeval {
long tv_sec; /* seconds */
long tv_usec; /* and microseconds */
};
#endif
So unless you have defined LWIP_TIMEVAL_PRIVATE timeval will be
declared. However all this is inside #ifndef FD_SET so that could be
the cause of the problem.
Please provide a test case that i can compile and see the error.
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
prev parent reply other threads:[~2006-04-10 17:54 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 ` [ECOS] Possible omission in Lwip? Birahim Larou Fall
2006-04-09 11:41 ` Andrew Lunn
2006-04-10 15:35 ` Birahim Larou Fall
2006-04-10 17:54 ` Andrew Lunn [this message]
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=20060410175416.GB8017@lunn.ch \
--to=andrew@lunn.ch \
--cc=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).