[oe] busybox-static linking failed

Khem Raj raj.khem at gmail.com
Fri Oct 30 20:05:40 UTC 2009


On Fri, Oct 30, 2009 at 8:28 AM, Steffen Sledz <sledz at dresearch.de> wrote:
> On 10/29/2009 11:29 PM, Khem Raj wrote:
>>> 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. :(
>>
>> you need this kernel patch here
>> http://lkml.org/lkml/2009/6/18/223
>
> This fixes the missing include inside the kernel. My patch suggestion
> adds the missing include inside busybox. I would prefer the kernel
> patch. Any objections?

This patch have not been applied in kernel upstream yet. So it would
be nice to get
an idea if this will be pushed upstream or not. Otherwise patching
busybox will be
right thing to do. May be you can ping the author of kernel patch to
retry to push
it

Thanks

-Khem

>
> Steffen
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>




More information about the Openembedded-devel mailing list