From: David Ahern <dsahern@gmail.com>
To: Irina Tirdea <irina.tirdea@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 02/13] perf tools: update types definitions for Android
Date: Wed, 29 Aug 2012 10:18:07 -0600 [thread overview]
Message-ID: <503E40BF.8090905@gmail.com> (raw)
In-Reply-To: <CANg8OWJnDvd28KTZffojhxLds4znjTTq294=H-_frbX6dStaWw@mail.gmail.com>
On 8/28/12 4:33 PM, Irina Tirdea wrote:
> Some systems (e.g. Android) define in their libc types.h
> __le16, __be16, etc. Since perf is wrapping
> <linux/types.h> with a local version, we need to define this
> constants in the local version too.
>
> Errors in Android:
> In file included from bionic/libc/include/netinet/in.h:34:0,
> from util/util.h:73,
> from util/cache.h:5,
> from util/abspath.c:1:
> bionic/libc/kernel/common/linux/in6.h:20:2: error: unknown type name '__be16'
> bionic/libc/kernel/common/linux/in6.h:21:2: error: unknown type name '__be32'
> bionic/libc/kernel/common/linux/in6.h:30:2: error: unknown type name '__be16'
> bionic/libc/kernel/common/linux/in6.h:31:2: error: unknown type name '__be32'
> bionic/libc/kernel/common/linux/in6.h:47:2: error: unknown type name '__be32'
This https://lkml.org/lkml/2012/8/29/150 should fix the netinet/in.h
build problem.
David
next prev parent reply other threads:[~2012-08-29 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-28 22:33 [PATCH 02/13] perf tools: update types definitions for Android Irina Tirdea
2012-08-29 16:18 ` David Ahern [this message]
2012-09-02 19:59 ` Irina Tirdea
-- strict thread matches above, loose matches on Subject: below --
2012-08-28 21:59 Irina Tirdea
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=503E40BF.8090905@gmail.com \
--to=dsahern@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=fweisbec@gmail.com \
--cc=irina.tirdea@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.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).