public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001098] LwIP compilation error with SNMP enable Date: Thu, 16 Dec 2010 19:21:00 -0000 [thread overview] Message-ID: <20101216185354.E0BB62F78007@mail.ecoscentric.com> (raw) In-Reply-To: <bug-1001098-777@http.bugs.ecos.sourceware.org/> Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001098 John Dallaway <john@dallaway.org.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEEDINFO CC| |john@dallaway.org.uk AssignedTo|unassigned@bugs.ecos.source |john@dallaway.org.uk |ware.org | Ever Confirmed|0 |1 --- Comment #1 from John Dallaway <john@dallaway.org.uk> 2010-12-16 18:53:53 GMT --- Christophe, the build error arises because IP_FORWARD is used in C code directly rather than being tested by the pre-processor. So it looks like your patch needs tweaking as follows: #ifdef CYGFUN_LWIP_IP_FORWARD # define IP_FORWARD 1 #endif Otherwise the build error will still occur when CYGFUN_LWIP_IP_FORWARD is enabled. Do you agree? (no need to re-generate the patch) -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
next prev parent reply other threads:[~2010-12-16 18:54 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-15 2:00 [Bug 1001098] New: " bugzilla-daemon 2010-12-16 19:21 ` bugzilla-daemon [this message] -- strict thread matches above, loose matches on Subject: below -- 2010-12-10 19:16 bugzilla-daemon 2010-12-16 18:54 ` [Bug 1001098] " bugzilla-daemon 2010-12-16 21:37 ` bugzilla-daemon 2010-12-18 11:21 ` 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=20101216185354.E0BB62F78007@mail.ecoscentric.com \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=unassigned@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).