public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-bugs@ecos.sourceware.org Subject: [Bug 1001873] Patches to upgrade lwip to 1.4.1 Date: Tue, 25 Feb 2014 15:44:00 -0000 [thread overview] Message-ID: <bug-1001873-13-opx5MTBFrW@http.bugs.ecos.sourceware.org/> (raw) In-Reply-To: <bug-1001873-13@http.bugs.ecos.sourceware.org/> Please do not reply to this email, use the link below. http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001873 Will Wagner <willw@carallon.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |MODIFIED --- Comment #27 from Will Wagner <willw@carallon.com> --- Hi Ilija, We actually did some work on this at the end of last year, but then it got lost in amongst other things. (In reply to comment #25) > > 1. Compilation of tests breaks on compiling the PPP test. The following > lwip_net.cdl hack makes it compile: > > calculated { "tests/httpd_sequential tests/httpd_simple " . > - "tests/nc_test_slave tests/ppp " . > + "tests/nc_test_slave " . > "tests/socket tests/sys_timeout tests/tcpecho " . > "tests/udpecho" } > > This is, however, a workaround rather than fix. The PPP test program should > be either fixed (synchronised with PPP upgrade) or, if obsolete, removed > completely. We have a patch I'll attach shortly that removes the test. Neither of us who have worked on this are in any way ppp experts, however we felt it was just not possible to port the test to the new version of lwip so we have removed it. > > 2. There are still some compiler warnings ( GCC 4.6.3 - eCos GNU Tools > 4.6.3-20120623 ) We see no warnings (CodeConfidence tools GCC 4.3.2). If you give details we can try to take a look at them. > > 3. There's no ChangeLog record. Will attach patch shortly > > 4. Copyright banners of eCos specific files that you have touched should be > updated. Will attach patch shortly -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-02-25 15:44 UTC|newest] Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-28 6:50 [Bug 1001873] New: " bugzilla-daemon 2013-06-28 6:50 ` [Bug 1001873] " bugzilla-daemon 2013-06-28 6:50 ` bugzilla-daemon 2013-06-28 6:51 ` bugzilla-daemon 2013-06-28 6:51 ` bugzilla-daemon 2013-06-28 6:51 ` bugzilla-daemon 2013-06-28 6:51 ` bugzilla-daemon 2013-06-28 6:52 ` bugzilla-daemon 2013-06-28 6:52 ` bugzilla-daemon 2013-06-30 22:03 ` bugzilla-daemon 2013-07-01 11:54 ` bugzilla-daemon 2013-07-01 11:55 ` bugzilla-daemon 2013-07-01 11:56 ` bugzilla-daemon 2013-07-01 11:56 ` bugzilla-daemon 2013-07-01 11:56 ` bugzilla-daemon 2013-07-01 11:56 ` bugzilla-daemon 2013-07-01 11:57 ` bugzilla-daemon 2013-07-01 11:57 ` bugzilla-daemon 2013-07-01 11:57 ` bugzilla-daemon 2013-07-01 11:58 ` bugzilla-daemon 2013-07-01 13:34 ` bugzilla-daemon 2013-08-09 16:13 ` bugzilla-daemon 2013-08-10 15:51 ` bugzilla-daemon 2013-09-06 7:01 ` bugzilla-daemon 2013-09-06 7:01 ` bugzilla-daemon 2014-02-25 15:44 ` bugzilla-daemon [this message] 2014-02-25 15:46 ` bugzilla-daemon 2014-02-25 15:47 ` bugzilla-daemon 2014-02-25 15:48 ` bugzilla-daemon 2014-02-25 15:48 ` bugzilla-daemon 2014-02-25 15:48 ` bugzilla-daemon 2014-02-25 15:49 ` bugzilla-daemon 2014-02-25 15:49 ` bugzilla-daemon 2014-02-25 15:50 ` bugzilla-daemon 2014-02-25 16:09 ` bugzilla-daemon 2014-02-25 16:09 ` bugzilla-daemon 2014-03-12 9:17 ` bugzilla-daemon 2014-03-12 9:36 ` bugzilla-daemon 2014-05-05 23:08 ` bugzilla-daemon 2014-06-04 14:38 ` bugzilla-daemon 2014-06-05 10:06 ` bugzilla-daemon 2014-06-06 7:46 ` bugzilla-daemon 2014-06-10 8:27 ` bugzilla-daemon 2014-06-10 11:05 ` bugzilla-daemon -- strict thread matches above, loose matches on Subject: below -- 2013-06-28 6:50 [Bug 1001873] New: " bugzilla-daemon 2013-06-28 6:50 ` [Bug 1001873] " bugzilla-daemon 2013-06-28 6:50 ` bugzilla-daemon 2013-06-28 6:51 ` bugzilla-daemon 2013-06-28 6:51 ` bugzilla-daemon 2013-06-28 6:51 ` bugzilla-daemon 2013-06-28 6:51 ` bugzilla-daemon 2013-06-28 6:52 ` bugzilla-daemon 2013-06-28 6:52 ` bugzilla-daemon 2013-06-30 22:03 ` bugzilla-daemon 2013-07-01 11:54 ` bugzilla-daemon 2013-07-01 11:55 ` bugzilla-daemon 2013-07-01 11:55 ` bugzilla-daemon 2013-07-01 11:56 ` bugzilla-daemon 2013-07-01 11:56 ` bugzilla-daemon 2013-07-01 11:56 ` bugzilla-daemon 2013-07-01 11:57 ` bugzilla-daemon 2013-07-01 11:57 ` bugzilla-daemon 2013-07-01 11:57 ` bugzilla-daemon 2013-07-01 11:58 ` bugzilla-daemon 2013-07-01 13:34 ` bugzilla-daemon 2013-08-09 16:13 ` bugzilla-daemon 2013-08-10 15:51 ` bugzilla-daemon 2013-09-06 7:00 ` bugzilla-daemon 2013-09-06 7:01 ` bugzilla-daemon 2013-09-13 20:30 ` bugzilla-daemon 2014-02-15 2:58 ` bugzilla-daemon 2014-02-25 15:44 ` bugzilla-daemon 2014-02-25 15:46 ` bugzilla-daemon 2014-02-25 15:47 ` bugzilla-daemon 2014-02-25 15:48 ` bugzilla-daemon 2014-02-25 15:48 ` bugzilla-daemon 2014-02-25 15:48 ` bugzilla-daemon 2014-02-25 15:49 ` bugzilla-daemon 2014-02-25 15:49 ` bugzilla-daemon 2014-02-25 15:50 ` bugzilla-daemon 2014-02-25 16:09 ` bugzilla-daemon 2014-02-25 16:09 ` bugzilla-daemon 2014-03-11 22:25 ` bugzilla-daemon 2014-05-07 14:57 ` bugzilla-daemon 2014-06-04 14:38 ` bugzilla-daemon 2014-06-06 7:46 ` bugzilla-daemon 2014-06-10 8:27 ` bugzilla-daemon
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=bug-1001873-13-opx5MTBFrW@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=ecos-bugs@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: linkBe 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).