[U-Boot] [PATCH] display the entry point when compiling a stand-alone program
Contrary to popular belief, the entry point for a stand-alone program is not consistent. The only way to know for sure is to use the nm program and search for the entry point function. So we update the Makefile build rule to display this entry point after the ELF image is created.
Signed-off-by: Timur Tabi timur@freescale.com --- examples/standalone/Makefile | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/examples/standalone/Makefile b/examples/standalone/Makefile index 6ea3b93..d6a01ea 100644 --- a/examples/standalone/Makefile +++ b/examples/standalone/Makefile @@ -83,6 +83,7 @@ $(obj)%: $(obj)%.o $(LIB) $(LD) -g -Ttext $(STANDALONE_LOAD_ADDR) \ -o $@ -e $(SYM_PREFIX)$(notdir $(<:.o=)) $< $(LIB) \ -L$(gcclibdir) -lgcc + $(NM) $@ | grep $@
$(SREC): $(obj)%.srec: $(obj)%
Hi Timur,
Contrary to popular belief, the entry point for a stand-alone program is not consistent. The only way to know for sure is to use the nm program and search for the entry point function. So we update the Makefile build rule to display this entry point after the ELF image is created.
Signed-off-by: Timur Tabi timur@freescale.com
I was thinking along the same lines but decided that this is not the correct solution but only sweetening the fall ;)
We should concentrate on creating a correct linker script so that the entry point ends up where we want it to be, namely at STANDALONE_LOAD_ADDR.
Can you have a look at this and maybe solve the problem for good then?
Thanks! Detlev
Detlev Zundel wrote:
We should concentrate on creating a correct linker script so that the entry point ends up where we want it to be, namely at STANDALONE_LOAD_ADDR.
Can you have a look at this and maybe solve the problem for good then?
I have no idea how to do that. I don't know diddly about linker scripts.
participants (2)
-
Detlev Zundel -
Timur Tabi