[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51FEF88E.3070902@mybluelight.com>
Date: Sun, 04 Aug 2013 17:57:50 -0700
From: Kirk Terrell <knjterrell@...luelight.com>
To: musl@...ts.openwall.com
Subject: Re: Embedded distro
On 08/04/2013 04:40 AM, Rich Felker wrote:
> On Sat, Aug 03, 2013 at 07:56:35PM -0700, Kirk Terrell wrote:
>>>>> what needs these header hacks?
>>>>>
>>>>> cp ${CLFS}/usr/include/linux/if_slip.h ${CLFS}/usr/include/net/if_slip.h
>>>>> cp ${CLFS}/usr/include/net/if_arp.h ${CLFS}/usr/include/linux/if_arp.h
>>>>>
>>>> I did this because busybox complained about header locations - these
>>>> are headers from the kernel, not from Musl. This issue did not
>>>> present when building a similar system using uClibc.
>>> I wasn't aware of these issues. Which files are they in? Maybe we
>>> should look into getting this fixed upstream...
>>>
>> The headers were to address the following issues that occurred while
>> compiling busybox1.18.4. I'm using GCC-4.6.0 and Musl 0.9.11. I've
>> passed the extra cflags -D_GNU_SOURCE -Dfdprintd=dprintf. My target
>> is armel-unknown-linux-gnueabi. While compiling busybox I got the
>> following errors:
>>
>>> CC networking/ifconfig.o
>>> networking/ifconfig.c:43:26: fatal error: net/if_slip.h: No such
>>> file or directory
>>> compilation terminated.
>> After turning off ifconfig I get the following:
>>
>>> networking/libiproute/ll_types.c:11:26: fatal error:
>>> linux/if_arp.h: No such file or directory
>>> compilation terminated.
>> Since these headers come from the kernel and not Musl I suspect its
>> a busybox issue. Any insight would be appreciated.
> Like John said in his reply to you, you're using an ancient version of
> Busybox with lots of known bugs, some of which are especially
> problematic if you'll be using the busybox utilities in place of
> coreutils when running programs' configure scripts and building
> software. I would recommend upgrading to latest busybox. As far as I
> know, it has all the issues against musl fixed, as well as having
> fixes for the bugs I just mentioned.
>
> Rich
>
>
I tried the most recent version of busybox and had the same issue, and
so I looked a little further:
> excerpt from busybox networking/ifconfig.c
> if ENABLE_FEATURE_IFCONFIG_SLIP
> # include <net/if_slip.h>
> #endif
>
> clfs-kanj:~/sources/musl-0.9.11/include/net$ ls
> ethernet.h if.h if_arp.h route.h
>
> clfs-kanj:~/sources/uClibc-0.9.31/include/net$ ls
> ethernet.h if_arp.h if_ppp.h if_slip.h ppp_defs.h
> if.h if_packet.h if_shaper.h ppp-comp.h route.h
>
> from sabatoge-master/KEEP/busybox.patch
>
> #if ENABLE_FEATURE_IFCONFIG_SLIP
> -# include <net/if_slip.h>
> +# include <linux/if_slip.h>
> #endif
>
To me it appears that uClibc is installing headers, that busybox expects
to see, that Musl does not install. I am attempting to use Musl as far
as possible as drop in replacement. I will update to a recent version of
Busybox.
Kirk
____________________________________________________________
Stand With Our President
Show your support for raising the minimum wage. Sign the petition!
http://thirdpartyoffers.netzero.net/TGL3341/51fef88b8b830788a3f5fst01vuc
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
