Re: a separate build of libc

[Pierre Pronchery <khorben%defora.org@localhost>]

			Hi Rune,

I do not have the time to read the entire thread now, but you may want
to check the DeforaOS libc, which supports NetBSD (and Linux (and
more)). You can find it there:

http://www.defora.org/os/project/14/libc
http://git.defora.org/gitweb/?p=libc.git;a=summary
(or git clone http://git.defora.org/DeforaOS/libc.git)

Let me know if you need any help with it.

HTH,
-- khorben

On 19/09/2014 16:04, u-6hol%aetey.se@localhost wrote:
> Background:
> 
>   building an independent/standalone toolchain able to produce binaries
>   runnable on NetBSD
>   (note, this is not the same as compiling or cross-compiling "NetBSD")
> 
> The component:
> 
>   libc
> 
> A small practical question:
> 
>   Where does machine/asm.h come from, given the NetBSD source sets as
>   the starting point?
> 
> Presumably it is possible to find out the answer by analysing the
> "build.sh" tool but the named tool is possibly not the (only) definition
> of the structure/interrelations of the concerned data?
> 
> A deeper question:
> 
>   What would be the minimal initial data (source) to be able to recreate
>   a working NetBSD libc? I get the impression that the data is widely
>   scattered across different file trees and source sets, my goal
>   is now to identify the relevant subset of "the whole".
> 
> To better describe what I have in mind, I might refer to the source archive
> of musl Linux libc, which includes everything (including all includes :)
> that is needed for the build, as a single archive of less than 1MB.
> The compiler and linker to be used do not have to be platform-specific
> beyond the capability to build executables in a format understandable
> by the target kernel.
> 
> I don't see that there is any similar abstraction for NetBSD libc yet (?).
> It would be pretty useful.
> 
> Anybody who can/would answer the questions above?
> 
> Regards,
> Rune

-- 
khorben