DCCP protocol discussions
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: dccp@vger.kernel.org
Subject: Re: 2.6.16-rc4-mm1
Date: Mon, 20 Feb 2006 14:11:36 +0000	[thread overview]
Message-ID: <43F9CE18.10709@trash.net> (raw)

Reuben Farrelly wrote:
> Minor dependency issue:
> 
> My compile failed with this..
> 
>   CC [M]  net/netfilter/xt_dccp.o
> In file included from net/netfilter/xt_dccp.c:15:
> include/linux/dccp.h:341:2: error: #error "At least one CCID must be
> built as the default"
> make[2]: *** [net/netfilter/xt_dccp.o] Error 1
> make[1]: *** [net/netfilter] Error 2
> make: *** [net] Error 2
> [root@tornado linux-2.6-mm]#
> 
> [I have no idea what a CCID is]
> 
> But it was caused by this:
> 
> CONFIG_NETFILTER_XT_MATCH_DCCP=m
> 
> and maybe this below had an impact:
> 
> #
> # DCCP Configuration (EXPERIMENTAL)
> #
> # CONFIG_IP_DCCP is not set
> 
> After unsetting the option to build the DCCP Netfilter module, I was
> able to compile through to completion.

Ideally this dependency should be enforced by Kconfig. I'm not sure
if it is possible to express something like "IP_DCCP_CCID2 and
IP_DCCP_CCID3 depend on DCCP, DCCP requires at least one of both
to be enabled". Can someone more familiar with Kconfig than me
comment on this? Otherwise the #error should be moved to
net/dccp/options.c to keep dccp.h usable without dccp enabled.

             reply	other threads:[~2006-02-20 14:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20 14:11 Patrick McHardy [this message]
2006-02-20 14:20 ` 2.6.16-rc4-mm1 Arnaldo Carvalho de Melo
2006-02-20 20:04 ` 2.6.16-rc4-mm1 Carl-Daniel Hailfinger
2006-02-20 20:44 ` 2.6.16-rc4-mm1 Adrian Bunk
2006-02-20 20:56 ` 2.6.16-rc4-mm1 Arnaldo Carvalho de Melo
2006-02-20 21:09 ` 2.6.16-rc4-mm1 Adrian Bunk

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=43F9CE18.10709@trash.net \
    --to=kaber@trash.net \
    --cc=dccp@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox