public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jamie Iles <jamie.iles@picochip.com>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Jamie Iles <jamie.iles@picochip.com>,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] perf tools: allow cross compiling with DWARF support
Date: Fri, 25 Jun 2010 12:41:50 +0100	[thread overview]
Message-ID: <20100625114150.GE4510@wear.picochip.com> (raw)
In-Reply-To: <4C249027.1060304@hitachi.com>

On Fri, Jun 25, 2010 at 08:16:55PM +0900, Masami Hiramatsu wrote:
> Jamie Iles wrote:
> > The path to elfutils was previously hardcoded as /usr/include/elfutils
> > which does not work with cross compilers. If CROSS_COMPILE is set, try
> > to set an include path from GCC's sysroot if GCC was built with sysroot
> > support, if sysroot support isn't enabled, don't specify a path for
> > elfutils allowing the user to set it with EXTRA_CFLAGS.
> 
> Hmm, I'm not so sure about cross compiling. I just thought
> if there is no sysroot support, we should warn user instead of
> just failing to find elfutils.
Is that something that you really need to warn the user about? If they have a
compiler without sysroot support they can still cross compile using
EXTRA_CFLAGS and the warning would be needless. There isn't a real requirement
for sysroot here, just a path to the elfutils headers.

Jamie

  reply	other threads:[~2010-06-25 11:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-25 10:38 [PATCH] perf tools: allow cross compiling with DWARF support Jamie Iles
2010-06-25 11:16 ` Masami Hiramatsu
2010-06-25 11:41   ` Jamie Iles [this message]
2010-06-25 12:03     ` Masami Hiramatsu
2010-06-25 13:33       ` Jamie Iles
2010-06-28  1:34         ` Masami Hiramatsu

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=20100625114150.GE4510@wear.picochip.com \
    --to=jamie.iles@picochip.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    /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