Blackfin: propagate target cpu defines when building embedded env

Since we're no longer extracting the env from the target ELF file (since
upstream wouldn't take that change), we're back to the problem of cpu
defines not properly propagating to the env setup stage.  So the embedded
env built by the host compiler doesn't match the one that is linked into
the u-boot env.

Reported-by: Vivi Li <vivi.li@analog.com>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
This commit is contained in:
Mike Frysinger 2010-09-26 07:00:38 +00:00
parent cec11d5014
commit 48c00fe25c

View file

@ -43,6 +43,9 @@ ALL += $(obj)u-boot.ldr
endif endif
ifeq ($(CONFIG_ENV_IS_EMBEDDED_IN_LDR),y) ifeq ($(CONFIG_ENV_IS_EMBEDDED_IN_LDR),y)
CREATE_LDR_ENV = $(obj)tools/envcrc --binary > $(obj)env-ldr.o CREATE_LDR_ENV = $(obj)tools/envcrc --binary > $(obj)env-ldr.o
HOSTCFLAGS_NOPED += \
$(shell $(CPP) -dD - -mcpu=$(CONFIG_BFIN_CPU) </dev/null \
| awk '$$2 ~ /ADSP/ { print "-D" $$2 }')
else else
CREATE_LDR_ENV = CREATE_LDR_ENV =
endif endif