What is the rationale behind removing crt0.o from gcc4.7.x?

Question

I am trying to upgrade to yagarto4.7.2 (Yet Another GNU ARM toolchain, for those wondering), which is gcc and binutils, ported for Windows. However, trying to compile a simple Hello World yields:

c:/yagarto-20121222/bin/../lib/gcc/arm-none-eabi/4.7.2/../../../../arm-none-eabi
/bin/ld.exe: cannot find crt0.o: No such file or directory
collect2.exe: error: ld returned 1 exit status

Now, in this forum it is made clear that this is the startup initialziation library, that was removed after gcc4.6.x. Two solutions are proposed:

• compile with -nostartfiles
• copy the crt0.o form the 4.6.x to the 4.7.x folder

Both look quite dirty and unacceptable for production code. So does anyone know why was this library removed and what is it's equivalent now?

Tetchy

Some key facts about yargarto; a mingw based newlib compiler, pre-built. See: SO gcc newlib questions. It is possible to build this type of compiler with crosstool-ng, but is extremely difficult as it is a Canadian cross. – Lambaste

#18417064 – Modification

Answer 1

crt0.o is derived from crt0.s, which is provided by the OS. In the case of bare metal setup, this file must be provided by the implementation. It contains startup and exit code, for example for zeroing the .bss.

Tetchy

Not so silly - it generated discussions on a forum, which you've provided a link to. SO also functions as a knowledge base, and you should feel free to accept your own answer. – Besnard

Documentation on these funtions: Newlib syscalls including minimal implementations. – Lambaste

So where did you got crt0.s for what OS? – Gnarly

@harper, see the above comment by artless noise for instructions how to write your own. – Tetchy