This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
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
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |