From: Sergei Poselenov <sposelenov@emcraft.com>
To: linux-kernel@vger.kernel.org
Cc: wd@denx.de
Subject: [PATCH] Fix userland build failure in linux/if_tunnel.h
Date: Thu, 18 Jun 2009 18:37:38 +0400 [thread overview]
Message-ID: <20090618183738.662f7ef1@emcraft.com> (raw)
Hello all,
The last commit to linux/if_tunnel.h broke the busybox
application build.
When linking the final image linker complains:
networking/libiproute/lib.a(iptunnel.o): In function `parse_args':
/work/psl/e/arm-aa/target_rpms/busybox/BUILD/busybox-1.7.1/networking/libiproute/iptunnel.c:189:
undefined reference to
`__cpu_to_be16' /work/psl/e/arm-aa/target_rpms/busybox/BUILD/busybox-1.7.1/networking/libiproute/iptunnel.c:190:
undefined reference to
`__cpu_to_be16' /work/psl/e/arm-aa/target_rpms/busybox/BUILD/busybox-1.7.1/networking/libiproute/iptunnel.c:202:
undefined reference to `__cpu_to_be16'
...
Please review the following patch, which fixes the build error.
Subject: [PATCH] The busybox application build failed in linking complaining to unresolved
__cpu_to_be16 (ARM target). This patch fixes this.
Signed-off-by: Sergei Poselenov <sposelenov@emcraft.com>
---
include/linux/if_tunnel.h | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/include/linux/if_tunnel.h b/include/linux/if_tunnel.h
index 5a9aae4..137130b 100644
--- a/include/linux/if_tunnel.h
+++ b/include/linux/if_tunnel.h
@@ -2,6 +2,7 @@
#define _IF_TUNNEL_H_
#include <linux/types.h>
+#include <asm/byteorder.h>
#ifdef __KERNEL__
#include <linux/ip.h>
--
1.6.0.6
next reply other threads:[~2009-06-18 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 14:37 Sergei Poselenov [this message]
2009-08-07 11:31 ` Sergei Poselenov
2009-08-07 16:03 ` David Miller
2009-08-07 16:43 ` [PATCH] MAINTAINERS: additional NETWORKING [GENERAL] and NETWORKING DRIVERS patterns Joe Perches
2009-08-10 4:47 ` David Miller
2009-08-07 17:01 ` [PATCH] REPORTING-BUGS: Add get_maintainer.pl blurb Joe Perches
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=20090618183738.662f7ef1@emcraft.com \
--to=sposelenov@emcraft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wd@denx.de \
/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
all inboxes | Powered by JetHome®