All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amos Jeffries <squid3@treenet.co.nz>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: C++ compile errors
Date: Mon, 01 Jul 2013 23:16:09 +1200	[thread overview]
Message-ID: <51D164F9.9030201@treenet.co.nz> (raw)
In-Reply-To: <20130630161411.GA28817@localhost>

On 1/07/2013 4:14 a.m., Pablo Neira Ayuso wrote:
> Hi Amos,
>
> On Sun, Jun 30, 2013 at 07:35:26PM +1200, Amos Jeffries wrote:
>> Can anyone update me on whether this submission or an equivalent fix
>> ever made it into the formal releases? and if so which ones?
>> https://lkml.org/lkml/2012/9/30/146
> The solution for this is to cache the modified header (that compiles
> with C++) in your application source code tree. We cannot take changes
> to get C++ application compiling, sorry.

Really? The application I'm working with is only trying to use 
getsockopt() interface with IP6T_SO_ORIGINAL_DST. Nothing more.

/usr/include/linux/netfilter_ipv6/ip6_tables.h: In function 
'xt_entry_target* ip 6t_get_target(ip6t_entry*)':
/usr/include/linux/netfilter_ipv6/ip6_tables.h:261:19: error: invalid 
conversion from 'void*' to 'xt_entry_target*' [-fpermissive]
   return (void *)e + e->target_offset;
                    ^

Restricting all users of the published headers to C-compilers is a bit 
annoying. Good way to prevent anyone using IPv6 with NAT though ;-)

Amos

      reply	other threads:[~2013-07-01 11:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-30  7:35 C++ compile errors Amos Jeffries
2013-06-30 16:14 ` Pablo Neira Ayuso
2013-07-01 11:16   ` Amos Jeffries [this message]

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=51D164F9.9030201@treenet.co.nz \
    --to=squid3@treenet.co.nz \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.