Re: [PATCH] Do not set CROSS_COMPILE but let CONFIG_CROSS_COMPILE handle it all.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tuesday, May 24, 2011 13:47:01 Jeroen Roovers wrote:
> Do not set CROSS_COMPILE but let CONFIG_CROSS_COMPILE handle it all.
> The problem this fixes manifests itself when you try to build a 64-bit
> kernel on a distro which does not provide hppa$(WIDTH)-linux-gnu- but
> perhaps hppa$(WIDTH)-unknown-linux-gnu- instead, like Gentoo Linux.
> 
> --- a/arch/parisc/Makefile
> +++ b/arch/parisc/Makefile
> @@ -31,16 +31,10 @@
>  UTS_MACHINE	:= parisc64
>  CHECKFLAGS	+= -D__LP64__=1 -m64
>  WIDTH		:= 64
> -CROSS_COMPILE	:= hppa64-linux-gnu-
>  else # 32-bit
>  WIDTH		:=
>  endif
> 
> -# attempt to help out folks who are cross-compiling
> -ifeq ($(NATIVE),1)
> -CROSS_COMPILE	:= hppa$(WIDTH)-linux-
> -endif

i wonder if there isnt some middle ground.  like only setting CROSS_COMPILE 
like so:
ifeq ($(CROSS_COMPILE),)
CROSS_COMPILE := hppa$(WIDTH)-linux-
endif

i think that should still work if people set CONFIG_CROSS_COMPILE, but if they 
havent, get the existing (semi-sane) defaults.
-mike

Attachment: signature.asc
Description: This is a digitally signed message part.


[Index of Archives]     [Linux SoC]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux