public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, 2nddept-manager@sdl.hitachi.co.jp
Subject: Re: [PATCH -perf/perf/makefile  0/2] Perf bugfixes for cross-builds
Date: Sun, 27 Feb 2011 18:43:55 +0900	[thread overview]
Message-ID: <4D6A1CDB.4040908@hitachi.com> (raw)
In-Reply-To: <20110222121139.GB27070@ghostprotocols.net>

(2011/02/22 21:11), Arnaldo Carvalho de Melo wrote:
> Em Tue, Feb 22, 2011 at 09:04:18PM +0900, Masami Hiramatsu escreveu:
>> Hi Arnaldo,
>>
>> BTW, could you pull these patches for cross building?
> 
> I'll try again to use this new feature, sorry for not sending feedback,
> but I failed to use it on a RHEL6 system, have to try again and provide
> proper feedback.

Hmm, would you install some devel packages for i686 too?
This change requires 32bits devel packages for cross building.

Thank you,

>  
>> (2011/02/10 11:28), Masami Hiramatsu wrote:
>>> Hi,
>>>
>>> Here are some bugfixes related to cross builds.
>>> - Introduce ARCH=XX for cross-builds instead of obsolate
>>>   EXTRA_CFLAGS=-mXX option.
>>> - Rename obsolate NO_PERL to NO_LIBPERL
>>>
>>> Still not sure how I can do cross-builds i386 binary with
>>> perl/python support on x86-64. Anyway, now we can do without
>>> that as below;
>>>
>>>  $ make ARCH=i386 NO_LIBPERL=1 NO_LIBPYTHON=1
>>>
>>> Thank you,
>>>
>>> ---
>>>
>>> Masami Hiramatsu (2):
>>>       perf tools: Rename old NO_PERL option to NO_LIBPERL
>>>       perf tools: Introduce ARCH= option for cross building
>>>
>>>
>>>  tools/perf/Makefile              |   48 +++++++++++++++++++++++++-------------
>>>  tools/perf/arch/arm/Makefile     |    2 +-
>>>  tools/perf/arch/powerpc/Makefile |    2 +-
>>>  tools/perf/arch/s390/Makefile    |    2 +-
>>>  tools/perf/arch/sh/Makefile      |    2 +-
>>>  tools/perf/arch/sparc/Makefile   |    2 +-
>>>  tools/perf/arch/x86/Makefile     |    2 +-
>>>  7 files changed, 38 insertions(+), 22 deletions(-)
>>>
>>
>>
>> -- 
>> Masami HIRAMATSU
>> 2nd Dept. Linux Technology Center
>> Hitachi, Ltd., Systems Development Laboratory
>> E-mail: masami.hiramatsu.pt@hitachi.com


-- 
Masami HIRAMATSU
2nd Dept. Linux Technology Center
Hitachi, Ltd., Systems Development Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com

  reply	other threads:[~2011-02-27  9:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-10  2:28 [PATCH -perf/perf/makefile 0/2] Perf bugfixes for cross-builds Masami Hiramatsu
2011-02-10  2:28 ` [PATCH -perf/perf/makefile 1/2] perf tools: Introduce ARCH= option for cross building Masami Hiramatsu
2011-02-10  2:29 ` [PATCH -perf/perf/makefile 2/2] perf tools: Rename old NO_PERL option to NO_LIBPERL Masami Hiramatsu
2011-02-22 12:04 ` [PATCH -perf/perf/makefile 0/2] Perf bugfixes for cross-builds Masami Hiramatsu
2011-02-22 12:11   ` Arnaldo Carvalho de Melo
2011-02-27  9:43     ` Masami Hiramatsu [this message]
2011-02-27 10:27       ` Arnaldo Carvalho de Melo

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=4D6A1CDB.4040908@hitachi.com \
    --to=masami.hiramatsu.pt@hitachi.com \
    --cc=2nddept-manager@sdl.hitachi.co.jp \
    --cc=acme@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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