From: "Michael Grimard" <michaelg@maxt.com>
To: <ecos-discuss@sourceware.org>
Subject: RE: [ECOS] Trouble using lwIP (driver crash...)
Date: Tue, 04 Apr 2006 13:20:00 -0000 [thread overview]
Message-ID: <000c01c657ea$8acbbe90$8c0a0a0a@cygnus> (raw)
In-Reply-To: <443195C2.2000606@web.de>
Hi,
When I compile without the File IO package I got:
In file included from
/my_path_to_ecos/ecos/packages/infra/current/src/diag.cxx:65:
/my_path_to_ecos/ecos_lwip_install/include/limits.h:175:37:
cyg/fileio/limits.h: No such file or directory
For nc_test_slave, I got the "Not Applicable" message when I ran it, but I
didn't try it before running nc_test_master, since nc_test_slave is part of
the tests that come with lwIP. Maybe, it needs to be remove?
Michael
-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Uwe Kindler
Sent: April 3, 2006 5:38 PM
To: ecos-discuss@sourceware.org
Cc: michaelg@maxt.com
Subject: Re: [ECOS] Trouble using lwIP (driver crash...)
Hello,
which file does include cyg/fileio/limits.h? I searched the whole lwIP
stack sources but did not found any file that includes limits.h.
The nc_test_slave is currently not applicable because SO_REUSEADDR and
SO_REUSEPORT are not supported at the moment and the nc_test_slave
requires both.
Regards, Uwe
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
--
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-04 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 23:02 Uwe Kindler
2006-04-04 13:20 ` Michael Grimard [this message]
2006-04-04 13:33 ` Andrew Lunn
2006-04-04 14:36 ` Michael Grimard
-- strict thread matches above, loose matches on Subject: below --
2006-04-04 15:45 Uwe Kindler
2006-04-04 17:10 ` Michael Grimard
2006-04-05 7:26 ` Birahim Larou Fall
2006-04-03 13:14 Michael Grimard
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='000c01c657ea$8acbbe90$8c0a0a0a@cygnus' \
--to=michaelg@maxt.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).