From: Patrick McHardy <kaber@trash.net>
To: F Helmer <netfilter.20.fhelmer@spamgourmet.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: rtsp conntrack compilation error 2.6.18
Date: Wed, 10 Jan 2007 07:10:10 +0100 [thread overview]
Message-ID: <45A48342.1050601@trash.net> (raw)
In-Reply-To: <loom.20061225T094953-80@post.gmane.org>
F Helmer wrote:
> Hello
>
> I am not sure if this is the correct group to post to?
>
> I am trying to patch my 2.6.18 kernel (latest pom using svn + runme extra)
> and I
> get the following compilation error:
>
> CC [M] net/ipv4/netfilter/ip_conntrack_netlink.o
> CC [M] net/ipv4/netfilter/ip_conntrack_proto_sctp.o
> CC [M] net/ipv4/netfilter/ip_conntrack_rtsp.o
> net/ipv4/netfilter/ip_conntrack_rtsp.c: In function 'help_out':
> net/ipv4/netfilter/ip_conntrack_rtsp.c:340: error: too few arguments
> to function
> 'ip_conntrack_expect_alloc'
> net/ipv4/netfilter/ip_conntrack_rtsp.c:371: warning: implicit declaration of
> function 'ip_conntrack_expect_free'
> make[4]: *** [net/ipv4/netfilter/ip_conntrack_rtsp.o] Error 1
> make[3]: *** [net/ipv4/netfilter] Error 2
> make[2]: *** [net/ipv4] Error 2
> make[1]: *** [net] Error 2
> make[1]: Leaving directory `/usr/src/linux-source-2.6.18'
> make: *** [debian/stamp-build-kernel] Error 2
> fredrikh@helmer:/usr/src/linux$
>
> Do you happen to know what I am doing wrong? Or is there a "better"
> patch somewhere?
The patch needs to be updated to work with current kernels. Its
not actively maintained, so you'll probably have to do it yourself.
next prev parent reply other threads:[~2007-01-10 6:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-25 8:50 rtsp conntrack compilation error 2.6.18 F Helmer
2007-01-10 6:10 ` Patrick McHardy [this message]
2007-01-24 16:54 ` Sverker Abrahamsson
2007-01-24 17:38 ` Patrick McHardy
2007-01-25 16:37 ` Steven Van Acker
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=45A48342.1050601@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=netfilter.20.fhelmer@spamgourmet.com \
/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.