[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51FD4870.1000902@mybluelight.com>
Date: Sat, 03 Aug 2013 11:14:08 -0700
From: Kirk Terrell <knjterrell@...luelight.com>
To: musl@...ts.openwall.com
Subject: Re: Embedded distro
On 08/03/2013 09:43 AM, Szabolcs Nagy wrote:
> * Kirk Terrell <knjterrell@...luelight.com> [2013-08-03 09:19:22 -0700]:
>> I've been working on a distro that is a fork from the CLFS Embedded
>> project that uses musl libc in place of libc. I've managed to boot
>> an emulated Vexpress-a9 target using the instructions at
>> http://kanj.github.io/elfs/book/armMusl/index.html.
>>
> is the --host really the CLFS_TARGET? should it be renamed in the configure script?
>
> CROSS_COMPILE=${CLFS_TARGET}- ./configure --prefix=${CLFS} --disable-gcc-wrapper \
> --host=${CLFS_TARGET} --build=${CLFS_HOST} --syslibdir=${CLFS}/lib --includedir=${CLFS}/usr/include
According to ./configure --help
System types:
--target=TARGET configure to run on target TARGET [detected]
--host=HOST same as --target
I think --host is legitimate but is confusing. I should look into
changing this.
>
> 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.
Thank you for the feedback.
kirk
____________________________________________________________
RN to BSN Online Option
Earn Your RN To BSN in 3 Semesters. Online, Affordable & User Friendly
http://thirdpartyoffers.netzero.net/TGL3341/51fd482e7e5c1482b4672st04duc
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.
