From: Filip Sneppe <filip.sneppe@uptime.be>
To: Andy Furniss <andy.furniss@dsl.pipex.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: mms and rtsp patches = make modules fail
Date: 30 Jan 2004 01:31:13 +0100 [thread overview]
Message-ID: <1075422674.17013.8.camel@exile> (raw)
In-Reply-To: <40190E1F.6090700@dsl.pipex.com>
Hi,
On Thu, 2004-01-29 at 14:43, Andy Furniss wrote:
> I just tested on a different machine, same old distro, though.
>
> vanilla 2.4.24(I didn't patch this time) same POM (3 days old now) did
> ./runme extra (last time I did make dep first)
>
> and said y to connlimit nth quota u32 connbytes mms-conntrack-nat
> rtsp-conntrack string and it said this -
With these patches, my 2.4.24 compiles fine when doing a
"make SUBDIRS=net/ipv4/netfilter modules"
> Already applied: connlimit nth quota u32 connbytes conntrack-seqfile
> conntrack_arefcount conntrack_locking conntrack_nonat mms-conntrack-nat
> netfilter-docbook owner-socketlookup owner-supgids ownercmd
> rtsp-conntrack string
Where do conntrack-seqfile, conntrack_arefcount, and these other
patches come from ? You must have selected them at one point in
time during a POM run, as they don't get applied automatically.
The list of patches mentioned in "Already applied: " step on
each other - in fact, in current CVS, POM warns against this and
one can only apply them all by forcing POM to apply some of them.
I get a compilation error afterwards, not the same as you, but
this probably depends on the order in which these patches have
been applied on our systems.
> make mrproper (should I do this here?)
It's ok to do a make mrproper here
Regards,
Filip
next prev parent reply other threads:[~2004-01-30 0:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 13:39 mms and rtsp patches = make modules fail Andy Furniss
2004-01-29 9:28 ` Filip Sneppe
2004-01-29 13:43 ` Andy Furniss
2004-01-30 0:31 ` Filip Sneppe [this message]
2004-01-30 12:44 ` Andy Furniss
2004-01-30 12:53 ` Filip Sneppe
2004-01-30 14:25 ` Andy Furniss
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=1075422674.17013.8.camel@exile \
--to=filip.sneppe@uptime.be \
--cc=andy.furniss@dsl.pipex.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox