All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Kyle McMartin <kyle@mcmartin.ca>,
	linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH] parisc: autoselect 32/64bit compiler
Date: Wed, 18 Feb 2009 00:12:10 +0100	[thread overview]
Message-ID: <499B444A.8070009@gmx.de> (raw)
In-Reply-To: <4999DEF6.4070300@gmx.de>

Helge Deller wrote:
> Automatically select correct 32- or 64bit (cross) compiler, independent if
> the kernel is built locally (e.g. 64bit kernel target on 32bit userspace) or 
> cross-compiled from another architecture. This patch allows one to just
> run 
> 	make ARCH=parisc	when run as cross compiler, or just
> 	make 			when run locally.
> 
> Signed-off-by: Helge Deller <deller@gmx.de>

Just ignore/drop this patch.
Although IMHO the idea is good, it breaks if people name their
(cross-)compiler "hppa-linux-gcc" instead of "hppa-linux-gnu-gcc".

Helge


> diff --git a/arch/parisc/Makefile b/arch/parisc/Makefile
> index da6f669..9d0bd90 100644
> --- a/arch/parisc/Makefile
> +++ b/arch/parisc/Makefile
> @@ -22,23 +22,12 @@ KBUILD_DEFCONFIG := default_defconfig
>  NM		= sh $(srctree)/arch/parisc/nm
>  CHECKFLAGS	+= -D__hppa__=1
>  
> -MACHINE		:= $(shell uname -m)
> -ifeq ($(MACHINE),parisc*)
> -NATIVE		:= 1
> -endif
> -
>  ifdef CONFIG_64BIT
>  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-
> +CROSS_COMPILE	:= hppa-linux-gnu-
>  endif
>  
>  OBJCOPY_FLAGS =-O binary -R .note -R .comment -S
> 


      reply	other threads:[~2009-02-17 23:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16 21:47 [PATCH] parisc: autoselect 32/64bit compiler Helge Deller
2009-02-17 23:12 ` Helge Deller [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=499B444A.8070009@gmx.de \
    --to=deller@gmx.de \
    --cc=kyle@mcmartin.ca \
    --cc=linux-parisc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.