From: David Ahern <dsahern@gmail.com>
To: Vinson Lee <vlee@twopensource.com>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-perf-users@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 4.0-rc1 perf build error "builtin-kmem.c:322: error: declaration of ‘stat’ shadows a global declaration"
Date: Fri, 24 Apr 2015 07:54:50 -0600 [thread overview]
Message-ID: <553A4B2A.7090703@gmail.com> (raw)
In-Reply-To: <CAHTgTXUA6T0yX9CpwZZJ43UKNfZQzx2PCw_hJTsNeOSm0nZTyA@mail.gmail.com>
On 4/23/15 6:38 PM, Vinson Lee wrote:
> Hi.
>
> 4.0-rc1 commit 0d68bc92c48167130b61b449f08be27dc862dba2 "perf kmem:
> Analyze page allocator events also" introduced a build error with
> older toolchains.
>
> For example, this build errors occurs on CentOS 6.
>
> CC builtin-kmem.o
> cc1: warnings being treated as errors
> builtin-kmem.c: In function ‘search_page_alloc_stat’:
> builtin-kmem.c:322: error: declaration of ‘stat’ shadows a global declaration
> /usr/include/sys/stat.h:455: error: shadowed declaration is here
> builtin-kmem.c: In function ‘perf_evsel__process_page_alloc_event’:
> builtin-kmem.c:378: error: declaration of ‘stat’ shadows a global declaration
> /usr/include/sys/stat.h:455: error: shadowed declaration is here
> builtin-kmem.c: In function ‘perf_evsel__process_page_free_event’:
> builtin-kmem.c:431: error: declaration of ‘stat’ shadows a global declaration
> /usr/include/sys/stat.h:455: error: shadowed declaration is here
Fixed in Arnaldo's core branch; he will push to urgent and Ingo soon.
David
prev parent reply other threads:[~2015-04-24 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 0:38 4.0-rc1 perf build error "builtin-kmem.c:322: error: declaration of ‘stat’ shadows a global declaration" Vinson Lee
2015-04-24 13:54 ` David Ahern [this message]
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=553A4B2A.7090703@gmail.com \
--to=dsahern@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=vlee@twopensource.com \
/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.