From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Cc: mlauer@vanille-media.de
Subject: busybox-static linking failed
Date: Wed, 28 Oct 2009 12:54:06 +0100 [thread overview]
Message-ID: <4AE830DE.5030209@dresearch.de> (raw)
After a long time i tried to build an initramfs image containing
busybox-static which fails to link (besides some warnings) with these
errors:
/home/OE/tmp.3/work/armv5te-angstrom-linux-gnueabi/busybox-static-1.11.3-r22.1/busybox-1.11.3/networking/libiproute/iptunnel.c:189:
undefined reference to `__cpu_to_be16'
/home/OE/tmp.3/work/armv5te-angstrom-linux-gnueabi/busybox-static-1.11.3-r22.1/busybox-1.11.3/networking/libiproute/iptunnel.c:190:
undefined reference to `__cpu_to_be16'
/home/OE/tmp.3/work/armv5te-angstrom-linux-gnueabi/busybox-static-1.11.3-r22.1/busybox-1.11.3/networking/libiproute/iptunnel.c:202:
undefined reference to `__cpu_to_be16'
/home/OE/tmp.3/work/armv5te-angstrom-linux-gnueabi/busybox-static-1.11.3-r22.1/busybox-1.11.3/networking/libiproute/iptunnel.c:214:
undefined reference to `__cpu_to_be16'
/home/OE/tmp.3/work/armv5te-angstrom-linux-gnueabi/busybox-static-1.11.3-r22.1/busybox-1.11.3/networking/libiproute/iptunnel.c:224:
undefined reference to `__cpu_to_be16'
networking/libiproute/lib.a(iptunnel.o):/home/OE/tmp.3/work/armv5te-angstrom-linux-gnueabi/busybox-static-1.11.3-r22.1/busybox-1.11.3/networking/libiproute/iptunnel.c:225:
more undefined references to `__cpu_to_be16' follow
This is really obscure for me because i can't identify the code lines
responsible for them. :(
Steffen
next reply other threads:[~2009-10-28 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 11:54 Steffen Sledz [this message]
2009-10-29 12:07 ` [PATCH 2/2] busybox-1.11.3: undefined reference __cpu_to_be16 fixed for busybox-static Steffen Sledz
2009-10-29 22:29 ` busybox-static linking failed Khem Raj
2009-10-30 15:28 ` Steffen Sledz
2009-10-30 20:05 ` Khem Raj
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=4AE830DE.5030209@dresearch.de \
--to=sledz@dresearch.de \
--cc=mlauer@vanille-media.de \
--cc=openembedded-devel@lists.openembedded.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.