From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Jamie Iles <jamie.iles@picochip.com>
Cc: 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 21:03:34 +0900 [thread overview]
Message-ID: <4C249B16.2090209@hitachi.com> (raw)
In-Reply-To: <20100625114150.GE4510@wear.picochip.com>
Jamie Iles wrote:
> 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.
It seems that $ELFUTILS_INCLUDE become "" without sysroot support.
In that case, I guess that user have to set the elfutils header
path to EXTRA_CFLAGS and, make will just show "No libdw.h found
or old libdw.h found ..." message. (I just guess, not so familier
with cross compile...)
So, I just like to suggest adding a message like as;
"No sysroot support. Please set elfutils include path in EXTRA_CFLAGS."
Doesn't it make easier to find a problem?
Other parts are OK for me.
Thank you,
next prev parent reply other threads:[~2010-06-25 12:03 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
2010-06-25 12:03 ` Masami Hiramatsu [this message]
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=4C249B16.2090209@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=a.p.zijlstra@chello.nl \
--cc=jamie.iles@picochip.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox