Document why we invoke gcc instead of directly invoking ld (trivial).
Signed-off-by: Uwe Hermann <uwe@hermann-uwe.de> Acked-by: Uwe Hermann <uwe@hermann-uwe.de> git-svn-id: svn://coreboot.org/repository/LinuxBIOSv3@282 f3766cd6-281f-0410-b1cd-43a5c92072e9
This commit is contained in:
parent
3dc564852f
commit
d0f42a9993
1 changed files with 3 additions and 0 deletions
|
|
@ -82,6 +82,9 @@ $(obj)/stage0.init: $(STAGE0_OBJ)
|
|||
$(Q)# 0x4000 - 0x100, we will end up with a 4 gig file.
|
||||
$(Q)# I wonder if that behavior is on purpose.
|
||||
|
||||
# Note: we invoke gcc (instead of ld directly) here, as we hit
|
||||
# strange problems in the past. It seems that only gcc knows how to
|
||||
# properly invoke ld.
|
||||
$(Q)printf " CC $(subst $(shell pwd)/,,$(@))\n"
|
||||
$(Q)$(CC) -nostdlib -static -T $(src)/arch/x86/ldscript.ld \
|
||||
$(STAGE0_OBJ) -o $(obj)/stage0.o
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue