This is the mail archive of the crossgcc@sources.redhat.com 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]

How to control location of startup code?


Somewhat off-topic, but I hope you'll forgive me (this list seems to be the best place to ask about this type of compiler/linker details):

Is there any way to control how the default startup code ends up in the output file/the virutal address it gets and/or what output section it's included in?

I've tried obvious things like
   crt0.o(.text*)
at the appropriate spot in the linker script, but this does not work.

With the above entry I get
/usr/arm-coff/bin/ld: cannot open crt0.o: No such file or directory

If I use e.g. crt0.o* instead of crt0.o, the link completes, but nothing changes (compared to not mentioning the crt0 file at all.)

--
Toralf


------ 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]