From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Embedded distro
Date: Sun, 4 Aug 2013 07:40:12 -0400 [thread overview]
Message-ID: <20130804114012.GX221@brightrain.aerifal.cx> (raw)
In-Reply-To: <51FDC2E3.7010807@mybluelight.com>
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
next prev parent reply other threads:[~2013-08-04 11:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-03 16:19 Kirk Terrell
2013-08-03 16:43 ` Szabolcs Nagy
2013-08-03 18:14 ` Kirk Terrell
2013-08-03 19:57 ` Rich Felker
2013-08-04 2:56 ` Kirk Terrell
2013-08-04 11:40 ` Rich Felker [this message]
2013-08-05 0:57 ` Kirk Terrell
2013-08-05 1:16 ` Rich Felker
2013-08-07 16:36 ` Rob Landley
2013-08-03 20:28 ` John Spencer
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=20130804114012.GX221@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).