From: "Daniel 'NebuchadnezzaR' Dehennin" <nebuchadnezzar@nerim.net>
To: Linux Net <netdev@oss.sgi.com>
Subject: [IPV6] problem with xfrm6_tunnel_check_size
Date: Sun, 12 Oct 2003 14:04:12 +0200 [thread overview]
Message-ID: <87vfquslvn.fsf@nerim.net> (raw)
Hello,
I try to compile a 2.6.0-test7 with usagi 20031012 but I have the following
error:
net/built-in.o(.text+0x599f3): dans la fonction « xfrm_check_output »:
: undefined reference to `xfrm6_tunnel_check_size'
make[1]: *** [.tmp_vmlinux1] Erreur 1
make[1]: Leaving directory `/usr/src/linux-2.6.0-test7'
make: *** [stamp-build] Erreur 2
I try to figure out the problem by myself but I don't manage to do it.
Here is what I do:
Search xfrm6_tunnel_check_size in net/:
net/ipv6/ipv6_syms.c:EXPORT_SYMBOL(xfrm6_tunnel_check_size);
net/ipv6/xfrm6_tunnel.c:int xfrm6_tunnel_check_size(struct sk_buff *skb)
net/ipv6/xfrm6_tunnel.c: if ((err = xfrm6_tunnel_check_size(skb)) != 0)
net/xfrm/xfrm_output.c: err = xfrm6_tunnel_check_size(skb);
Search xfrm6_tunnel_check_size in include/:
include/net/xfrm.h:extern int xfrm6_tunnel_check_size(struct sk_buff *skb);
Search xfrm4_tunnel_check_size in net/:
net/ipv4/xfrm4_tunnel.c:int xfrm4_tunnel_check_size(struct sk_buff *skb)
net/ipv4/xfrm4_tunnel.c: if ((err = xfrm4_tunnel_check_size(skb)) != 0)
net/xfrm/xfrm_export.c:EXPORT_SYMBOL(xfrm4_tunnel_check_size);
net/xfrm/xfrm_output.c: err = xfrm4_tunnel_check_size(skb);
Search xfrm4_tunnel_check_size in include/:
include/net/xfrm.h:extern int xfrm4_tunnel_check_size(struct sk_buff *skb);
I see that building xfrm we use xfrm_export in with
xfrm4_tunnel_check_size is exported but xfrm6_tunnel_check_size is in
ipv6/ip6_syms.c, is this a way to solve the problem ?
Is there a reason to have an ipv6_syms and not an ipv4_syms ?
Thanks.
--
Daniel 'NebuchadnezzaR' Dehennin
reply other threads:[~2003-10-12 12:04 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=87vfquslvn.fsf@nerim.net \
--to=nebuchadnezzar@nerim.net \
--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).