From: Aleksandar Milivojevic <amilivojevic@pbl.ca>
To: netfilter@lists.netfilter.org
Subject: unresolved symbols in ip_conntrack_rpc_udp.o
Date: Fri, 23 Apr 2004 13:54:48 -0500 [thread overview]
Message-ID: <40896678.5030106@pbl.ca> (raw)
Hi,
I've donwloaded rpc.patch and applied it against Red Hat's
kernel-source-2.4.20-24.7 package on my development machine. I've used
configs/kernel-2.4.20-i386.config as basic configuration file, and added
RPC match support under Netfilter Configuration. I've used i386 config
file, since I wanted to build modules that I could copy to other Linux
boxes I have, and not to have to worry about exact architecture.
When I copy three RPC modules (ip_conntrack_rpc_tcp.o,
ip_conntrack_rpc_udp.o and ipt_rpc.o) to
/lib/modules/kernel-version/kernel/net/ipv4/netfilter, and do depmode -a
everything is fine. All works if I copy those files to another test box
I have which is also i686 (same as devel box). However if I copy them
to i586 box, depmode complains about unresolved symbols, and if I try
modprobe, it says that irq_stat_R9c2e871c can't be resolved. The only
difference between two test boxes is that one is i686, and the other is
i586. This is kind of strange, why would code built for i386 work on
i686, and not on i586?
Is there a way to compile those modules so that I can use them on all my
boxes, regardless of exact architecture? Additionally, it would be nice
if there is a way to build them so that I can use them with different
2.4 revisions without recompiling.
--
Aleksandar Milivojevic <amilivojevic@pbl.ca> Pollard Banknote Limited
Systems Administrator 1499 Buffalo Place
Tel: (204) 474-2323 ext 276 Winnipeg, MB R3T 1L7
reply other threads:[~2004-04-23 18:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=40896678.5030106@pbl.ca \
--to=amilivojevic@pbl.ca \
--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.