Linux Netfilter development
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: "Gabor Z. Papp" <gzp@papp.hu>,
	Netfilter Development Mailinglist
	<netfilter-devel@vger.kernel.org>
Subject: Re: [netfilter-core] [ANNOUNCE] Release of iptables 1.4.1-rc2
Date: Thu, 05 Jun 2008 19:56:14 +0200	[thread overview]
Message-ID: <484828BE.7050209@trash.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0806051946330.29055@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> On Thursday 2008-06-05 19:19, Patrick McHardy wrote:
>   
>>>   CC       libxt_dccp.oo
>>> libxt_dccp.c:16:24: warning: linux/dccp.h: No such file or directory
>>>       
>> Mhh .. I don't really want to add that file to iptables.
>> Jan, I'm not familiar with auto*, could you send a patch
>> to make compilation of libxt_dccp dependand on the presence
>> of linux/dccp.h? Thanks.
>>     
>
> Is dccp.h too ugly?
I'd prefer to limit the included files to netfilter-related ones.

>  Either way, please pull from
> 	git://dev.medozas.de/xtables master
> to get
> commit 1ebc55e29f220082814a97e541427be7746400e0
> parent 324651944e03072cde144d41896b2e207672d0f2
> Author: Jan Engelhardt <jengelh@medozas.de>
> Date:   Thu Jun 5 19:48:31 2008 +0200
>
>     build: check for missing feature files
>
>     linux/dccp.h is unlikely to be installed before 2.6.18 (which was
>     when headers_install was introduced), and does not exist at all
>     before 2.6.14. Add a compile-time check to skip compilation of
>     libxt_dccp in case this was detected.
>   

Done, thanks.

Gabor, could you try again using the latest git version?



  parent reply	other threads:[~2008-06-05 17:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-26 13:01 [ANNOUNCE] Release of iptables 1.4.1-rc2 Patrick McHardy
2008-05-27  7:11 ` Gabor Z. Papp
2008-05-27  7:35   ` [netfilter-core] " Patrick McHardy
2008-05-27 12:10     ` Gabor Z. Papp
2008-05-27 13:11       ` Patrick McHardy
2008-05-28  6:40         ` Gabor Z. Papp
2008-05-28  6:43           ` Patrick McHardy
2008-06-05 14:21             ` Patrick McHardy
2008-06-05 17:11               ` Gabor Z. Papp
2008-06-05 17:19                 ` Patrick McHardy
2008-06-05 17:52                   ` Jan Engelhardt
2008-06-05 17:53                     ` Jan Engelhardt
2008-06-05 18:09                       ` Gabor Z. Papp
2008-06-05 18:10                         ` Jan Engelhardt
2008-06-05 18:13                         ` Patrick McHardy
2008-06-05 17:56                     ` Patrick McHardy [this message]
2008-05-30  7:33 ` Thomas Jarosch
2008-05-30  8:17   ` Jan Engelhardt
2008-05-30  8:26     ` Thomas Jarosch
2008-06-01 21:08     ` Patrick McHardy
2008-06-01 22:09       ` Jan Engelhardt
2008-06-02  9:09         ` Patrick McHardy

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=484828BE.7050209@trash.net \
    --to=kaber@trash.net \
    --cc=gzp@papp.hu \
    --cc=jengelh@medozas.de \
    --cc=netfilter-devel@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