CROSS_COMPILE is generally passed from the command line or by the environment variable because cross tools vary from user to user.
But, having some choices of often used CROSS_COMPILE seems reasonable.
$(call cc-cross-prefix, ...) returns the first prefix where a prefix$(CC) is found in PATH.
If your cross tools exist in the argument of $(call cc-cross-prefix, ...), you do not have to specify it explicitly.
Signed-off-by: Masahiro Yamada yamada.m@jp.panasonic.com ---
My question is which cross tools are popular enough to be added to the list.
In my opition, arm-linux-gnueabi-gcc is popular because it is distributed in Ubuntu.
On the other hand, I am not sure ppc_8xx-gcc is currently being used.
Which one should be to added/deleted to our default list. Your comments are very welcome. (I am not familiar with compilers very much.)
arch/arm/config.mk | 2 +- arch/microblaze/config.mk | 2 +- arch/powerpc/config.mk | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm/config.mk b/arch/arm/config.mk index 792cb43..c5fd22f 100644 --- a/arch/arm/config.mk +++ b/arch/arm/config.mk @@ -6,7 +6,7 @@ #
ifeq ($(CROSS_COMPILE),) -CROSS_COMPILE := arm-linux- +CROSS_COMPILE := $(call cc-cross-prefix, arm-linux- arm-linux-gnueabi-) endif
ifndef CONFIG_STANDALONE_LOAD_ADDR diff --git a/arch/microblaze/config.mk b/arch/microblaze/config.mk index cdb321a..dae74f8 100644 --- a/arch/microblaze/config.mk +++ b/arch/microblaze/config.mk @@ -9,7 +9,7 @@ #
ifeq ($(CROSS_COMPILE),) -CROSS_COMPILE := mb- +CROSS_COMPILE := $(call cc-cross-prefix, mb- microblaze-linux-) endif
CONFIG_STANDALONE_LOAD_ADDR ?= 0x80F00000 diff --git a/arch/powerpc/config.mk b/arch/powerpc/config.mk index e398f97..ac94b2e 100644 --- a/arch/powerpc/config.mk +++ b/arch/powerpc/config.mk @@ -6,7 +6,7 @@ #
ifeq ($(CROSS_COMPILE),) -CROSS_COMPILE := ppc_8xx- +CROSS_COMPILE := $(call cc-cross-prefix, ppc_8xx- powerpc-linux-) endif
CONFIG_STANDALONE_LOAD_ADDR ?= 0x40000