All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Samuel Díaz García" <samueldg@arcoscom.com>
To: netfilter@lists.netfilter.org
Subject: Suggestions for some patch-o-matic extensions (comment, ipp2p, random, etc...)
Date: Wed, 16 Feb 2005 23:19:41 +0100	[thread overview]
Message-ID: <4213C6FD.5080705@arcoscom.com> (raw)

In some extensions, I detected that before I apply patch-o-matic (last 
source package) without problems, i can compile kernel and kernel 
modules fine.

But when I try to compile iptables, i have a common error with some 
extensions:
    error: near initialization for `<struct_name>.<struct_member>'

Some of these extensions are:
    * comment
    * ipp2p
    * random (IPv6)

Thinking about it, I had applied successfully these extensions over 
1.2.11 iptables version, but with 1.3.0, seems that some structure 
declaration has been changed and these modules don't compile without a 
manual user modification of the sources.

The "manual modification" should be an explicit member initialization in 
the struct, but some modules need more revision.

Here is the warning exposed.

Good Luck


--
    Samuel Díaz García
     Director Gerente
ArcosCom Wireless, S.L.L.

mailto:samueldg@arcoscom.com
http://www.arcoscom.com

Móvil: 651 93 72 48
Tlfn.: 956 70 13 15
Fax:   956 70 34 83


             reply	other threads:[~2005-02-16 22:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-16 22:19 Samuel Díaz García [this message]
2005-02-16 22:55 ` Suggestions for some patch-o-matic extensions (comment, ipp2p, random, etc...) Samuel Díaz García
2005-02-16 23:15   ` Samuel Jean
     [not found]     ` <4213DB25.1080604@arcoscom.com>
2005-02-17  0:00       ` Samuel Jean

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=4213C6FD.5080705@arcoscom.com \
    --to=samueldg@arcoscom.com \
    --cc=netfilter@lists.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.