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] |
This shows that three libraries 'libc.a', 'libidt.a' and 'libgcc.a' will be linked against and also a startup object, 'crt0.o', will be taken with. The entry symbol name is '_start' and so on... You should have something like this ('idt.ld') made for your own target board. But maybe that is one of the already supported boards and you could use the linker script for that.
If your target board is not already supported anywhere, then your homework would be to produce the glue library for it too, implementing the 'read()', 'write()','open()', 'close()', 'lseek()' etc. low-level I/O-functions and those memory-handling routines in it.
If you only want to see your toolchain producing an executable for 'something', just use one of the already supported target boards as your 'real target' and toy with it. The GNU debugger, 'GDB', comes with a MIPS-simulator and it simulates at least a PMON monitor based target board. So running and debugging some MIPS programs on your host system without a real target board is fully possible.
------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |