This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Re: mips-elf target newlib
- From: "Shaun Jackman" <sjackman at gmail dot com>
- To: Niklaus <niklaus at gmail dot com>
- Cc: crossgcc at sources dot redhat dot com, newlib at sourceware dot org
- Date: Tue, 11 Apr 2006 17:22:53 -0600
- Subject: Re: mips-elf target newlib
- References: <85e0e3140604110844r7605b7e4wea60d6a37995506a@mail.gmail.com>
- Reply-to: "Shaun Jackman" <sjackman at gmail dot com>
I find it easiest to build a bare-metal target (xxx-elf, gcc + newlib)
in a unified tree. Extract the gcc sources and the newlib sources, and
move the newlib-1.x.x/newlib/ directory into the gcc-4.x.x/ directory.
You can then remove the newlib-1.x.x directory. Building the gcc-4.x.x
directory will now build both gcc and newlib.
Cheers,
Shaun
On 4/11/06, Niklaus <niklaus@gmail.com> wrote:
> Hi,
> I have built binutils and gcc (bootstrap --without-headers) for the
> target=mips-elf ,
> .
> Now i have to compile newlib for the same architecture. How do i do
> it . Has anyone here done it before.
>
> Usually for linux systems , i copy the kernel headers of the target
> architecture into the proper directory , then compile glibc with that
> headers for the target and then build complete gcc.
>
> But now i am wondering for bare-metal mips-elf target , how to build
> newlib and install headers and complete gcc. how do i produce a hello
> world executable like i did for glibc.
>
> Regards
> Nik