From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Simon Kallweit <simon.kallweit@intefo.ch>
Cc: Mandeep Sandhu <mandeepsandhu.chd@gmail.com>,
ecos-discuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] ecos + lwip
Date: Thu, 27 Aug 2009 14:47:00 -0000 [thread overview]
Message-ID: <20090827144737.GA26068@ubuntu.local> (raw)
In-Reply-To: <4A9693EC.1060809@intefo.ch>
On Thu, Aug 27, 2009 at 04:10:52PM +0200, Simon Kallweit wrote:
> Mandeep Sandhu wrote:
>> On Thu, Aug 27, 2009 at 7:21 PM, Mandeep
>> Sandhu<mandeepsandhu.chd@gmail.com> wrote:
>>>> Well there was actually a mistake. I did compile sio.c even when serial
>>>> support is not needed (no SLIP or PPP). The warnings in socket.h should not
>>>> matter, but I'll look into them.
>>>>
>>>>> $ find packages/ -name serialio.h
>>>>> packages/io/serial/v3_0/include/serialio.h
>>>> Headers in the eCos repository will not be found when compiling, only the
>>>> headers which are copied over to your build tree are recognized.
>>>>
>>>> Well I fixed the bug with sio.c
>>>>
>>>> Here is the fixed release:
>>>> http://download.westlicht.ch/lwip-20090827-1.tar.gz
>>
>> This one compiled all the way through (leaving a few "warnings")!!
>
> Good news! I'll look into these warnings in socket.c when I get some time.
Simon, all warning will go away if you enter CDL for LWIP_ERR_T, look,
please, at lwip/err.h. By default that is signed char (?!), so its
capacity is quite overflowed. I just tried an ugly addition in err.h
#define LWIP_ERR_T unsigned int
and that fixed all gcc complains in socket.c. I checked it, i.e. with that tweak
all package is compiled silently (arm-elf-gcc 4.3.2), just alone warning:
sequential.c:113: warning: âset_ip_addrâ defined but not used
Sergei
>
> Simon
--
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:[~2009-08-27 14:47 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 11:01 Mandeep Sandhu
2009-08-26 11:16 ` Simon Kallweit
2009-08-27 10:49 ` Mandeep Sandhu
2009-08-27 11:17 ` Simon Kallweit
2009-08-27 12:42 ` Mandeep Sandhu
2009-08-27 13:20 ` Mandeep Sandhu
2009-08-27 13:42 ` Simon Kallweit
2009-08-27 13:51 ` Mandeep Sandhu
2009-08-27 14:02 ` Mandeep Sandhu
2009-08-27 14:06 ` Simon Kallweit
2009-08-27 14:47 ` Sergei Gavrikov [this message]
2009-08-27 15:03 ` Sergei Gavrikov
2009-09-01 12:04 ` Mandeep Sandhu
2009-09-01 12:17 ` Simon Kallweit
2009-09-01 12:32 ` Mandeep Sandhu
2009-09-01 12:38 ` Simon Kallweit
2009-09-01 12:49 ` Mandeep Sandhu
2009-09-01 12:57 ` Simon Kallweit
2009-09-01 13:25 ` Mandeep Sandhu
2009-09-01 13:34 ` Simon Kallweit
2009-09-01 15:20 ` Mandeep Sandhu
2009-09-01 15:32 ` Simon Kallweit
2009-09-01 15:46 ` Mandeep Sandhu
2009-09-01 15:49 ` Simon Kallweit
2009-09-02 6:15 ` Mandeep Sandhu
2009-09-02 13:19 ` Mandeep Sandhu
2009-09-02 15:32 ` Simon Kallweit
2009-09-03 7:45 ` Mandeep Sandhu
2009-09-03 8:36 ` Simon Kallweit
2009-09-03 8:46 ` Mandeep Sandhu
2009-09-03 8:48 ` Simon Kallweit
2009-09-03 8:55 ` Mandeep Sandhu
2009-09-03 9:04 ` Simon Kallweit
2009-09-03 10:23 ` Mandeep Sandhu
2009-09-03 10:46 ` Sergei Gavrikov
2009-08-27 13:52 ` Sergei Gavrikov
2009-08-27 14:05 ` Simon Kallweit
2009-08-27 14:42 ` Bart Veer
2009-08-27 14:54 ` Sergei Gavrikov
2009-08-27 13:45 ` Sergei Gavrikov
2009-08-27 13:49 ` Mandeep Sandhu
2009-08-27 14:04 ` Simon Kallweit
-- strict thread matches above, loose matches on Subject: below --
2009-08-27 14:20 agfa prayoga s
[not found] <144735.17263.qm@web65404.mail.ac4.yahoo.com>
2009-08-27 14:11 ` Simon Kallweit
2009-07-30 13:10 Mandeep Sandhu
2009-07-30 13:51 ` Sergei Gavrikov
2009-07-31 5:44 ` Mandeep Sandhu
2009-07-31 18:56 ` Sergei Gavrikov
2009-08-02 17:24 ` Mandeep Sandhu
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=20090827144737.GA26068@ubuntu.local \
--to=sergei.gavrikov@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=mandeepsandhu.chd@gmail.com \
--cc=simon.kallweit@intefo.ch \
/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).