linux-kernel - Re: [PATCH] perf tools: allow cross compiling with DWARF support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100625114150.GE4510@wear.picochip.com>
Date:	Fri, 25 Jun 2010 12:41:50 +0100
From:	Jamie Iles <jamie.iles@...ochip.com>
To:	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Cc:	Jamie Iles <jamie.iles@...ochip.com>, linux-kernel@...r.kernel.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCH] perf tools: allow cross compiling with DWARF support

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/