From mboxrd@z Thu Jan 1 00:00:00 1970 From: Geert Uytterhoeven Subject: Re: [RFC] Get rid of SUBARCH Date: Thu, 22 Aug 2013 14:58:26 +0200 Message-ID: References: <1377073172-3662-1-git-send-email-richard@nod.at> <20130821195157.GA18191@merkur.ravnborg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <20130821195157.GA18191@merkur.ravnborg.org> Sender: linux-m68k-owner@vger.kernel.org To: Sam Ravnborg Cc: Richard Weinberger , Linux-Arch , Michal Marek , Ralf Baechle , Paul Mundt , Jeff Dike , Guan Xuetao , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , the arch/x86 maintainers , linux-kbuild , "linux-kernel@vger.kernel.org" , linux-m68k , Linux MIPS Mailing List , Linux-sh list , uml-devel List-Id: linux-arch.vger.kernel.org On Wed, Aug 21, 2013 at 9:51 PM, Sam Ravnborg wrote: >> > The series touches also m68k, sh, mips and unicore32. >> > These architectures magically select a cross compiler if ARCH != SUBARCH. >> > Do really need that behavior? >> >> This does remove functionality. >> It allows to build a kernel using e.g. "make ARCH=m68k". >> >> Perhaps this can be moved to generic code? Most (not all!) cross-toolchains >> are called $ARCH-{unknown-,}linux{,-gnu}. >> Exceptions are e.g. am33_2.0-linux and bfin-uclinux. > > Today you can specify CROSS_COMPILE in Kconfig. > With this we should be able to remove these hacks. The correct CROSS_COMPILE value depends on the host environment, not on the target configuration. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pb0-f41.google.com ([209.85.160.41]:32963 "EHLO mail-pb0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753597Ab3HVM60 (ORCPT ); Thu, 22 Aug 2013 08:58:26 -0400 MIME-Version: 1.0 In-Reply-To: <20130821195157.GA18191@merkur.ravnborg.org> References: <1377073172-3662-1-git-send-email-richard@nod.at> <20130821195157.GA18191@merkur.ravnborg.org> Date: Thu, 22 Aug 2013 14:58:26 +0200 Message-ID: Subject: Re: [RFC] Get rid of SUBARCH From: Geert Uytterhoeven Content-Type: text/plain; charset=UTF-8 Sender: linux-arch-owner@vger.kernel.org List-ID: To: Sam Ravnborg Cc: Richard Weinberger , Linux-Arch , Michal Marek , Ralf Baechle , Paul Mundt , Jeff Dike , Guan Xuetao , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , the arch/x86 maintainers , linux-kbuild , "linux-kernel@vger.kernel.org" , linux-m68k , Linux MIPS Mailing List , Linux-sh list , uml-devel Message-ID: <20130822125826.5jM_jmH11Za4EwfWjv-kyHvksEtzHjornvfwSKXYjm0@z> On Wed, Aug 21, 2013 at 9:51 PM, Sam Ravnborg wrote: >> > The series touches also m68k, sh, mips and unicore32. >> > These architectures magically select a cross compiler if ARCH != SUBARCH. >> > Do really need that behavior? >> >> This does remove functionality. >> It allows to build a kernel using e.g. "make ARCH=m68k". >> >> Perhaps this can be moved to generic code? Most (not all!) cross-toolchains >> are called $ARCH-{unknown-,}linux{,-gnu}. >> Exceptions are e.g. am33_2.0-linux and bfin-uclinux. > > Today you can specify CROSS_COMPILE in Kconfig. > With this we should be able to remove these hacks. The correct CROSS_COMPILE value depends on the host environment, not on the target configuration. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds