All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krishna Prasanth P <krishnap@teneoris.com>
To: netfilter@lists.netfilter.org
Subject: compilation problem with cuseeme patch.
Date: 12 Feb 2004 17:36:50 +0530	[thread overview]
Message-ID: <1076587638.1004.49.camel@krishnap> (raw)

Hi!!
 I'm trying to use cuseeme patch with netfilter and downloaded the patch
from the cvs repository.
While building the kernel with the new patch, i'm not able to do
linking. The reason is the cuseeme(ip_nat_cuseeme.c) is using function
ip_nat_mangle_udp_packet() function which is not defined.

Please let me know, if i'm missing some other things while adding the
patch.

Thanks in advance.


regards
-prasanth

Error dump while building the kernel:

net/network.o: In function `cuseeme_mangle_outgoing':
net/network.o(.text+0x4c498): undefined reference
to`ip_nat_mangle_udp_packet'
net/network.o(.text+0x4c498): relocation truncated to fit: R_ARM_PC24
ip_nat_mangle_udp_packet
net/network.o: In function `cuseeme_mangle_incoming':
net/network.o(.text+0x4c514): undefined reference to
`ip_nat_mangle_udp_packet'
net/network.o(.text+0x4c514): relocation truncated to fit: R_ARM_PC24
ip_nat_mangle_udp_packet
net/network.o(.text+0x4c56c): undefined reference to
`ip_nat_mangle_udp_packet'
net/network.o(.text+0x4c56c): relocation truncated to fit: R_ARM_PC24
ip_nat_mangle_udp_packet
net/network.o(.text+0x4c5f4): undefined reference to
`ip_nat_mangle_udp_packet'
net/network.o(.text+0x4c5f4): relocation truncated to fit: R_ARM_PC24
ip_nat_mangle_udp_packet
make[2]: *** [vmlinux] Error 1
make[2]: Leaving directory
`/home/krishnap/work/lsi/homebase/linux/linux-2.4.10'
make[1]: *** [obelix] Error 2
make[1]: Leaving directory `/home/krishnap/work/lsi/homebase/linux'






             reply	other threads:[~2004-02-12 12:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-12 12:06 Krishna Prasanth P [this message]
2004-02-15 13:41 ` compilation problem with cuseeme patch Filip Sneppe
2004-02-15 15:28 ` Harald Welte

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=1076587638.1004.49.camel@krishnap \
    --to=krishnap@teneoris.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 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.