From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8476] New: [lttng] Version 2.6.0 unusable with kernel v4.0.0
Date: Wed, 25 Nov 2015 16:22:56 +0000 (UTC) [thread overview]
Message-ID: <bug-8476-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=8476
Summary: [lttng] Version 2.6.0 unusable with kernel v4.0.0
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: All
Status: NEW
Severity: minor
Priority: P5
Component: Outdated package
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: baronju at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Generating a build using buildroot with linux kernel v4.0.0 and lttng packages
generates the following error :
CC [M]
/continuus/jb01445/hg/br-top/buildroot/output/build/lttng-modules-2.6.0/probes/lttng-probe-block.o
In file included from
/continuus/jb01445/hg/br-top/buildroot/output/build/lttng-modules-2.6.0/probes/../instrumentation/events/lttng-module/../../../probes/define_trace.h:136:0,
from
/continuus/jb01445/hg/br-top/buildroot/output/build/lttng-modules-2.6.0/probes/../instrumentation/events/lttng-module/kmem.h:380,
from
/continuus/jb01445/hg/br-top/buildroot/output/build/lttng-modules-2.6.0/probes/lttng-probe-kmem.c:42:
/continuus/jb01445/hg/br-top/buildroot/output/build/lttng-modules-2.6.0/probes/../instrumentation/events/lttng-module/../../../probes/lttng-events.h:180:6:
error: conflicting types for ?trace_mm_page_alloc_extfrag?
void trace_##_name(_proto);
^
/continuus/jb01445/hg/br-top/buildroot/output/build/lttng-modules-2.6.0/probes/../instrumentation/events/lttng-module/../../../probes/lttng-events.h:47:2:
note: in expansion of macro ?LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP?
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto),
PARAMS(args))
^
/continuus/jb01445/hg/br-top/buildroot/output/build/lttng-modules-2.6.0/probes/../instrumentation/events/lttng-module/../../../probes/lttng-events.h:107:2:
note: in expansion of macro ?LTTNG_TRACEPOINT_EVENT_MAP?
LTTNG_TRACEPOINT_EVENT_MAP(name, name, \
^
/continuus/jb01445/hg/br-top/buildroot/output/build/lttng-modules-2.6.0/probes/../instrumentation/events/lttng-module/../../../probes/../instrumentation/events/lttng-module/kmem.h:291:1:
note: in expansion of macro ?LTTNG_TRACEPOINT_EVENT?
LTTNG_TRACEPOINT_EVENT(mm_page_alloc_extfrag,
^
In file included from include/trace/events/kmem.h:8:0,
from
/continuus/jb01445/hg/br-top/buildroot/output/build/lttng-modules-2.6.0/probes/lttng-probe-kmem.c:31:
include/linux/tracepoint.h:169:21: note: previous definition of
?trace_mm_page_alloc_extfrag? was here
static inline void trace_##name(proto) \
^
include/linux/tracepoint.h:325:3: note: in expansion of macro ?__DECLARE_TRACE?
__DECLARE_TRACE(name, PARAMS(proto), PARAMS(args), 1, \
^
include/linux/tracepoint.h:459:2: note: in expansion of macro ?DECLARE_TRACE?
DECLARE_TRACE(name, PARAMS(proto), PARAMS(args))
^
include/trace/events/kmem.h:267:1: note: in expansion of macro ?TRACE_EVENT?
TRACE_EVENT(mm_page_alloc_extfrag,
^
make[4]: ***
[/continuus/jb01445/hg/br-top/buildroot/output/build/lttng-modules-2.6.0/probes/lttng-probe-kmem.o]
Error 1
It seems that lttng v2.6.0 does not work with "recent" kernel version. Using
lttng-modules 2.6.4, lttng-ust 2.6.4 and lttng-tools 2.6.1 seems to solve the
problem.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2015-11-25 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 16:22 bugzilla at busybox.net [this message]
2015-11-25 16:28 ` [Buildroot] [Bug 8476] [lttng] Version 2.6.0 unusable with kernel v4.0.0 bugzilla at busybox.net
2015-11-29 23:02 ` bugzilla at busybox.net
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=bug-8476-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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.