From: <wenzong.fan@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] perf: flag __SANE_USERSPACE_TYPES__ to include int-ll64.h for mips64
Date: Sat, 26 Oct 2013 03:53:15 -0400 [thread overview]
Message-ID: <cover.1382773654.git.wenzong.fan@windriver.com> (raw)
From: Wenzong Fan <wenzong.fan@windriver.com>
As the same reason to powerpc64, mips64 also need the flag:
PPC64 uses long long for u64 in the kernel, but powerpc's asm/types.h
prevents 64-bit userland from seeing this definition, instead defaulting
to u64 == long in userspace.
Perf want LL64, flag __SANE_USERSPACE_TYPES__ to get int-ll64.h.
Fix the below issue:
| tests/attr.c:71:4: error: format '%llu' expects argument of type 'long
long unsigned int', but argument 6 has type '__u64' [-Werror=format=]
| tests/attr.c:80:7: error: format '%llu' expects argument of type 'long
long unsigned int', but argument 4 has type '__u64' [-Werror=format=]
| attr->type, attr->config, fd) < 0) {
| ^
The following changes since commit 754e8768b69acba89bd6c3ba5dbe55b9df4d8083:
base.bbclass: fix nondeterministic PACKAGECONFIG processing order (2013-10-24 08:38:27 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib wenzong/perf
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=wenzong/perf
Wenzong Fan (1):
perf: flag __SANE_USERSPACE_TYPES__ to include int-ll64.h for mips64
meta/recipes-kernel/perf/perf.bb | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--
1.7.9.5
next reply other threads:[~2013-10-26 7:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-26 7:53 wenzong.fan [this message]
2013-10-26 7:53 ` [PATCH 1/1] perf: flag __SANE_USERSPACE_TYPES__ to include int-ll64.h for mips64 wenzong.fan
2013-10-30 3:49 ` Yang Shi
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=cover.1382773654.git.wenzong.fan@windriver.com \
--to=wenzong.fan@windriver.com \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.