From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] iptables: fix userspace compilation of ip tables with C++
Date: Wed, 29 Oct 2014 19:24:34 -0300 [thread overview]
Message-ID: <54516922.1070306@zacarias.com.ar> (raw)
In-Reply-To: <20141029223413.70abc05b@free-electrons.com>
On 10/29/2014 06:34 PM, Thomas Petazzoni wrote:
> Dear Matt Weber,
>
> On Mon, 13 Oct 2014 14:12:43 -0500, Matt Weber wrote:
>>
>> Signed-off-by: Matt Weber <matthew.weber@rockwellcollins.com>
>> ---
>> ...ix-userspace-compilation-of-ip_tables_c_h.patch | 43 ++++++++++++++++++++
>> 1 file changed, 43 insertions(+)
>> create mode 100644 package/iptables/iptables-03-fix-userspace-compilation-of-ip_tables_c_h.patch
>
> This patch apparently dates back from 2012. Why has it never been
> merged upstream? Also, I don't really understand the interaction
> between the kernel headers, and this include/linux/ header in iptables.
>
> Has the problem been reported upstream to iptables?
>
> Gustavo, an opinion?
It was posted to lkml & linux-netdev at first, Davem told to post to
netfilter-devel. That was done:
http://marc.info/?t=134904906300003&r=1&w=1
The logic seems right, C++ is more strict and triggers the issue.
It's an issue when dealing with netfilter rules from custom C++ code.
But it seems to have been rejected without much explanation:
http://patchwork.ozlabs.org/patch/188216/
Regards.
next prev parent reply other threads:[~2014-10-29 22:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 19:12 [Buildroot] [PATCH 1/1] iptables: fix userspace compilation of ip tables with C++ Matt Weber
2014-10-29 21:34 ` Thomas Petazzoni
2014-10-29 22:24 ` Gustavo Zacarias [this message]
2014-10-30 0:48 ` Matthew Weber
2014-11-18 13:48 ` Matthew Weber
2014-11-18 17:56 ` Yann E. MORIN
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=54516922.1070306@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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