public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	LKML <linux-kernel@vger.kernel.org>,
	He Kuang <hekuang@huawei.com>,
	David Ahern <david.ahern@oracle.com>
Subject: Re: [PATCH] perf tools: Fix build error on ARCH=i386/x86_64/sparc64
Date: Mon, 2 Mar 2015 10:56:00 +0100	[thread overview]
Message-ID: <20150302095600.GA4833@krava.brq.redhat.com> (raw)
In-Reply-To: <1425270663-10215-1-git-send-email-namhyung@kernel.org>

On Mon, Mar 02, 2015 at 01:31:03PM +0900, Namhyung Kim wrote:
> He Kuang reported that current perf tools failed to build when ARCH
> variable was given like above.  It was because the name is different
> that internal directory name.  I can see that David's sparc64 build
> has same problem.  So fix it by applying the sed conversion script to
> the command line ARCH variable also, and fixing the converted name
> there (i.e. i386/x86_64 -> x86, sparc64 -> sparc).
> 
> Reported-and-tested-by: He Kuang <hekuang@huawei.com>
> Cc: David Ahern <david.ahern@oracle.com>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>

Acked-by: Jiri Olsa <jolsa@kernel.org>

thanks,
jirka

> ---
>  tools/perf/config/Makefile.arch | 23 +++++------------------
>  1 file changed, 5 insertions(+), 18 deletions(-)
> 
> diff --git a/tools/perf/config/Makefile.arch b/tools/perf/config/Makefile.arch
> index ff95a68741d1..e9720571341d 100644
> --- a/tools/perf/config/Makefile.arch
> +++ b/tools/perf/config/Makefile.arch
> @@ -1,28 +1,15 @@
> +ifndef ARCH
> +ARCH := $(shell uname -m 2>/dev/null || echo not)
> +endif
>  
> -uname_M := $(shell uname -m 2>/dev/null || echo not)
> -
> -RAW_ARCH := $(shell echo $(uname_M) | sed -e s/i.86/i386/ -e s/sun4u/sparc64/ \
> +ARCH := $(shell echo $(ARCH) | sed -e s/i.86/x86/ -e s/x86_64/x86/ \
> +                                  -e s/sun4u/sparc/ -e s/sparc64/sparc/ \
>                                    -e s/arm.*/arm/ -e s/sa110/arm/ \
>                                    -e s/s390x/s390/ -e s/parisc64/parisc/ \
>                                    -e s/ppc.*/powerpc/ -e s/mips.*/mips/ \
>                                    -e s/sh[234].*/sh/ -e s/aarch64.*/arm64/ \
>                                    -e s/tile.*/tile/ )
>  
> -# Additional ARCH settings for x86
> -ifeq ($(RAW_ARCH),i386)
> -  ARCH ?= x86
> -endif
> -
> -ifeq ($(RAW_ARCH),x86_64)
> -  ARCH ?= x86
> -
> -  ifneq (, $(findstring m32,$(CFLAGS)))
> -    RAW_ARCH := x86_32
> -  endif
> -endif
> -
> -ARCH ?= $(RAW_ARCH)
> -
>  LP64 := $(shell echo __LP64__ | ${CC} ${CFLAGS} -E -x c - | tail -n 1)
>  ifeq ($(LP64), 1)
>    IS_64_BIT := 1
> -- 
> 2.2.2
> 

  reply	other threads:[~2015-03-02  9:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02  4:31 [PATCH] perf tools: Fix build error on ARCH=i386/x86_64/sparc64 Namhyung Kim
2015-03-02  9:56 ` Jiri Olsa [this message]
2015-03-02 15:03   ` Arnaldo Carvalho de Melo
2015-03-03  6:22 ` [tip:perf/core] perf tools: Fix build error on ARCH=i386/x86_64/ sparc64 tip-bot for Namhyung Kim

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=20150302095600.GA4833@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=david.ahern@oracle.com \
    --cc=hekuang@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox