This is the mail archive of the crossgcc@sourceware.cygnus.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more infromation.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: __main undefined symbol


Doug Evans wrote:
> 
> Matthew Majka writes:
>  > I was under the impression that the only reason that a file named crt0.o
>  > was only needed because it was specified in one of the default linker
>  > scripts installed with the compiler and using a different startup/boot
>  > file was simply a matter of writing your own linker script.  Can someone
>  > confirm this for me?
> 
> Close.  For many ports crt0 is passed to ld from gcc on the command line.
> By that I mean gcc passes crt0 to linker as an argument, it appears
> in ld's argv[].  That doesn't mean the _user_ has to specify crt0 when
> invoking gcc.

That makes sense.  I think for my embedded targets (i960-vxworks,
powerpc-vxworks, and m68k-coff) I tend to call ld directly, although I
doubt they require a crt0.o anyway.

Matt

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]