This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Building a Gcc cross-compiler for a new system (init not working)
- From: "Thomas Epperson" <epperson at doors-software dot com>
- To: "Ian Lance Taylor" <iant at google dot com>
- Cc: gcc-help at gcc dot gnu dot org
- Date: Mon, 13 Oct 2008 06:06:57 -0500
- Subject: Re: Building a Gcc cross-compiler for a new system (init not working)
- References: <3f9ff4db0810111454r721126ecl6af50601c5d948a8@mail.gmail.com> <3f9ff4db0810111459t1b2e85f1y4f3f9a2dde716643@mail.gmail.com> <m3od1qle5o.fsf@google.com> <3f9ff4db0810112214i39c41c26le855e6c1c3b6ab57@mail.gmail.com> <m3k5cdl61b.fsf@google.com>
>
> Please reply to the mailing list, not just to me. Thanks.
>
> crti.o and crtn.o will define the _init and _fini functions for you.
> If you can't use them, then you need to define them yourself. And
> then you need to arrange for your startup code to call _init.
>
> Different newlib targets do this in different ways. There is no
> uniformity. The relevant code often lives in the libgloss directory.
>
> Ian
>
Thanks, this is what I couldn't find. The i386 directory doesn't have
any mechanism for crti.o and crtn.o. Looks like I will be modifying
another directories and putting it there. The xstormy16 target looks
like a good candidate for this.