From: Laura Abbott <labbott@redhat.com>
To: Jiri Olsa <jolsa@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Stephane Eranian <eranian@google.com>
Cc: Florian Weimer <fweimer@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: perf build failure with newer glibc headers
Date: Wed, 12 Jun 2019 15:23:12 -0400 [thread overview]
Message-ID: <4c0a4264-7142-2e6d-540d-aa354700e0bb@redhat.com> (raw)
Hi,
While doing some build experiments, I found a compile failure with perf and jvmti:
BUILDSTDERR: gcc -Wp,-MD,./.xsk.o.d -Wp,-MT,xsk.o -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-jvmti/jvmti_agent.c:48:21: error: static declaration of 'gettid' follows non-static declaration
BUILDSTDERR: 48 | static inline pid_t gettid(void)
BUILDSTDERR: | ^~~~~~
BUILDSTDERR: In file included from /usr/include/unistd.h:1170,
BUILDSTDERR: from jvmti/jvmti_agent.c:33:
BUILDSTDERR: /usr/include/bits/unistd_ext.h:40:16: note: previous declaration of 'gettid' was here
BUILDSTDERR: 40 | extern __pid_t gettid (void) __THROW;
BUILDSTDERR: | ^~~~~~
This is with the newer glibc headers that came into Fedora earlier this week
(glibc-2.29.9000-27.fc31) It looks like the newer headers now define gettid
so the in file gettid no longer works. Note this was a custom build with
jvmti enabled as regular Fedora doesn't have it enabled which is why this
wasn't reported elsewhere.
I don't know enough about either the glibc headers or perf to make a suggestion
on how to fix this but I'm happy to test.
Thanks,
Laura
next reply other threads:[~2019-06-12 19:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 19:23 Laura Abbott [this message]
2019-06-12 20:56 ` Arnaldo Carvalho de Melo
2019-06-12 21:29 ` Jiri Olsa
2019-06-13 15:19 ` Arnaldo Carvalho de Melo
2019-06-13 19:24 ` Laura Abbott
2019-06-13 20:34 ` Arnaldo Carvalho de Melo
2019-06-13 20:44 ` Jiri Olsa
2019-06-13 21:54 ` Arnaldo Carvalho de Melo
2019-06-12 21:27 ` Jiri Olsa
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=4c0a4264-7142-2e6d-540d-aa354700e0bb@redhat.com \
--to=labbott@redhat.com \
--cc=acme@redhat.com \
--cc=eranian@google.com \
--cc=fweimer@redhat.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®