From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: pvp@tk.ru.acad.bg
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.22-git10 compile error
Date: Thu, 19 Jul 2007 08:50:12 +0200 [thread overview]
Message-ID: <20070719085012.19fa2df7@gondolin.boeblingen.de.ibm.com> (raw)
In-Reply-To: <469F048A.5070003@tk.ru.acad.bg>
On Thu, 19 Jul 2007 09:28:26 +0300,
Plamen Petrov <plamen.petrov@tk.ru.acad.bg> wrote:
> Hi, all!
>
> Just for the record - linux kernel version 2.6.22-git10 fails to build
> with the following error:
>
> In file included from net/netfilter/xt_connlimit.c:27:
> include/net/netfilter/nf_conntrack.h:99: error: field `ct_general' has
> incomplete type
> include/net/netfilter/nf_conntrack.h: In function `nf_ct_get':
> include/net/netfilter/nf_conntrack.h:163: error: structure has no member
> named `nfct'
> include/net/netfilter/nf_conntrack.h: In function `nf_ct_put':
> include/net/netfilter/nf_conntrack.h:170: error: implicit declaration of
> function `nf_conntrack_put'
> include/net/netfilter/nf_conntrack.h: In function `nf_ct_is_untracked':
> include/net/netfilter/nf_conntrack.h:252: error: structure has no member
> named `nfct'
> In file included from net/netfilter/xt_connlimit.c:28:
> include/net/netfilter/nf_conntrack_core.h: In function
> `nf_conntrack_confirm':
> include/net/netfilter/nf_conntrack_core.h:68: error: structure has no
> member named `nfct'
> make[2]: *** [net/netfilter/xt_connlimit.o] Error 1
> make[1]: *** [net/netfilter] Error 2
> make: *** [net] Error 2
This is fixed with commit 3fd8f9e4b6c184d03d340bc86630f700de967fa8.
next prev parent reply other threads:[~2007-07-19 6:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 6:28 2.6.22-git10 compile error Plamen Petrov
2007-07-19 6:50 ` Cornelia Huck [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-19 6:49 Fw: " David Miller
2007-07-19 7:01 ` David Miller
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=20070719085012.19fa2df7@gondolin.boeblingen.de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pvp@tk.ru.acad.bg \
/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.