Hello Detlev, Gerhard, Tom,
On Wed, 5 Mar 2014 08:37:54 -0500 Tom Rini trini@ti.com wrote:
On Wed, Mar 05, 2014 at 06:24:24PM +0900, Masahiro Yamada wrote:
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(-)
Looking at the kernel, mips is a better example of where this becomes a handy thing, over just a "stop passing CROSS_COMPILE". But that includes adding tool-archpref.
-- Tom
Actually, my motivation here was to emulate arch/$(ARCH)/Makefile of Linux Kernel. Some of them are already using cc-cross-prefix. And arch/mips/Makefile looked reasonable enough to me.
But if this patch is unwelcome to developers (it looks like so), I do not mind retracting it.
Best Regards Masahiro Yamada