Re: Embedded distro

[Rob Landley <rob@landley.net>]

[-- Attachment #1: Type: text/plain, Size: 1888 bytes --]

On 08/03/2013 01:14:08 PM, Kirk Terrell wrote:
> On 08/03/2013 09:43 AM, Szabolcs Nagy wrote:
>> * Kirk Terrell <knjterrell@mybluelight.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.

uClibc #includes the kernel headers in its own headers, and/or parses  
stuff out of them at build time. Thus you have to tell uClibc where the  
kernel headers are in order to build uClibc, so kernel headers are  
installed as part of the uClibc build process.

Musl doesn't use kernel headers. You can install them after the fact  
(attached is the script I use to do so), but musl itself is not  
involved in this.

Rob

[-- Attachment #2: whack2.sh --]
[-- Type: application/x-shellscript, Size: 435 bytes --]