From: Milian Wolff <milian.wolff@kdab.com>
To: kim.phillips@arm.com
Cc: linux-perf-users@vger.kernel.org
Subject: Re: cross compiling perf
Date: Mon, 27 Jun 2016 13:56:59 +0200 [thread overview]
Message-ID: <5203721.HQllVzS61Y@milian-kdab2> (raw)
In-Reply-To: <20160615154706.CC0A43F246@usa-sjc-imap-foss1.foss.arm.com>
[-- Attachment #1: Type: text/plain, Size: 825 bytes --]
On Wednesday, June 15, 2016 10:47:06 AM CEST Kim Phillips wrote:
> On Wed, 15 Jun 2016 16:24:52 +0200
>
> Milian Wolff <milian.wolff@kdab.com> wrote:
> > I'm trying to compile a more modern version of the user-space perf tools
> > for an arm64 embedded target. So far, no cigar.
>
> ...
>
> > config/Makefile:272: *** No gnu/libc-version.h found, please install
> > glibc-
> > dev[el]. Stop
>
> fwiw, I've had marginally greater success in the past by perfoming an
> arm64-cross 'make defconfig; make -C tools/perf clean perf' before
> switching to building fully-featured perfs natively.
Doing these steps lead me to the same erroneous output as before.
Thanks
--
Milian Wolff | milian.wolff@kdab.com | Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt Experts
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5903 bytes --]
next prev parent reply other threads:[~2016-06-27 11:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 14:24 cross compiling perf Milian Wolff
2016-06-15 15:47 ` Kim Phillips
2016-06-27 11:56 ` Milian Wolff [this message]
2016-06-16 16:11 ` Arnaldo Carvalho de Melo
2016-06-17 9:49 ` Milian Wolff
2016-06-17 11:00 ` Arnaldo Carvalho de Melo
2016-06-20 1:56 ` Wangnan (F)
2016-06-27 11:56 ` Milian Wolff
2016-08-03 20:56 ` Milian Wolff
2016-08-04 13:22 ` Arnaldo Carvalho de Melo
2016-08-04 15:02 ` Milian Wolff
2016-08-04 18:36 ` Arnaldo Carvalho de Melo
2016-08-04 21:58 ` Milian Wolff
2016-08-05 0:13 ` Arnaldo Carvalho de Melo
2016-08-12 10:48 ` Milian Wolff
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=5203721.HQllVzS61Y@milian-kdab2 \
--to=milian.wolff@kdab.com \
--cc=kim.phillips@arm.com \
--cc=linux-perf-users@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;
as well as URLs for NNTP newsgroup(s).