From: Jakub Bogusz <qboosh@pld-linux.org>
To: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: 2.6.8.1 - unresolved xfrm symbols in ip6_tunnel
Date: Tue, 17 Aug 2004 22:30:13 +0200 [thread overview]
Message-ID: <20040817203013.GA31993@satan.blackhosts> (raw)
I've just got:
if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.6.8.1; fi
WARNING: /lib/modules/2.6.8.1/kernel/net/ipv6/ip6_tunnel.ko needs unknown symbol xfrm6_tunnel_register
WARNING: /lib/modules/2.6.8.1/kernel/net/ipv6/ip6_tunnel.ko needs unknown symbol xfrm6_tunnel_deregister
with
CONFIG_IPV6_TUNNEL=m
and no XFRM (it wasn't selected by IPV6_TUNNEL and it's not possible to
select it standalone - XFRM is selected only by some options which
I don't use).
So I think that IPV6_TUNNEL should select or depend on XFRM...
or usage of the above symbols should depend on CONFIG_XFRM ||
CONFIG_XFRM_MODULE?
--
Jakub Bogusz http://cyber.cs.net.pl/~qboosh/
next reply other threads:[~2004-08-17 20:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 20:30 Jakub Bogusz [this message]
2004-08-17 21:00 ` 2.6.8.1 - unresolved xfrm symbols in ip6_tunnel Adrian Bunk
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=20040817203013.GA31993@satan.blackhosts \
--to=qboosh@pld-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).