Re: arm-gcc-ld warning

[Rick Sustek <rsustek at cisco dot com>]

When the linker emits a warning about no start symbol,
it is because it was not present within the group of
object modules being linked.

Normally, this is taken care of in the background by
the gcc compiler driver, which invokes the linker on
your behalf, and feeds it one or more runtime support
modules (e.g. crt0.o) which contain the _start symbol.

Thus I would guess you are invoking the linker directly,
and not giving it an object module which has the _start
symbol. Or, if you are only invoking gcc, then things
are not set up correctly to find the run-time support
modules.

The only thing the linker wants this _start symbol for
anyways, is to inject its value into the entry point
field of the execution header in the ELF file. You can
give the entry address explicitly to the linker on
the command line with the -e or --entry (I think?) flags.
Or you can ignore the warning. However, if the piece of
code which will execute the ELF file wants a proper entry
point value, you'd better get things in order.


Hope this helps,
Rick


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