From: bjorn.forsman@gmail.com (Bjørn Forsman)
Subject: [lttng-dev] lttng-modules build error against linux 3.18.x longterm kernels
Date: Sun, 12 Apr 2015 15:55:59 +0200 [thread overview]
Message-ID: <CAEYzJUGL6Q_o=zESuhhszBKGUCYrTwxBp32xppicQLZa6a4nVg@mail.gmail.com> (raw)
In-Reply-To: <CAEYzJUH27pYhSZmFEeaCQ7deeH75+GhjrVjdGN6dnyG+DyQhXA@mail.gmail.com>
On 26 March 2015 at 23:11, Bj?rn Forsman <bjorn.forsman at gmail.com> wrote:
> Hi all,
>
> (I'm not subscribed, please CC me.)
>
> Build error snippet:
>
> [...]
> CC [M] /tmp/nix-build-lttng-modules-2.6.0-5-g1b2a542-3.18.10.drv-0/lttng-modules-1b2a542/probes/lttng-probe-irq.o
> CC [M] /tmp/nix-build-lttng-modules-2.6.0-5-g1b2a542-3.18.10.drv-0/lttng-modules-1b2a542/probes/lttng-probe-timer.o
> CC [M] /tmp/nix-build-lttng-modules-2.6.0-5-g1b2a542-3.18.10.drv-0/lttng-modules-1b2a542/probes/lttng-probe-kmem.o
> In file included from
> /tmp/nix-build-lttng-modules-2.6.0-5-g1b2a542-3.18.10.drv-0/lttng-modules-1b2a542/probes/../instrumentation/events/lttng-module/../../../probes/define_trace.h:136:0,
> from
> /tmp/nix-build-lttng-modules-2.6.0-5-g1b2a542-3.18.10.drv-0/lttng-modules-1b2a542/probes/../instrumentation/events/lttng-module/kmem.h:466,
> from
> /tmp/nix-build-lttng-modules-2.6.0-5-g1b2a542-3.18.10.drv-0/lttng-modules-1b2a542/probes/lttng-probe-kmem.c:42:
> /tmp/nix-build-lttng-modules-2.6.0-5-g1b2a542-3.18.10.drv-0/lttng-modules-1b2a542/probes/../instrumentation/events/lttng-module/../../../probes/lttng-events.h:180:6:
> error: conflicting types for 'trace_mm_page_alloc_extfrag'
> void trace_##_name(_proto);
> ^
> /tmp/nix-build-lttng-modules-2.6.0-5-g1b2a542-3.18.10.drv-0/lttng-modules-1b2a542/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))
> [...]
>
> Build results from the NixOS build server[1] (which contains full
> logs) seems to indicate that this breakage started with the linux
> 3.18.9 -> 3.18.10 transition. Simultaneously, lttng-modules was
> updated 2.6.0-rc1 -> 2.6.0-5-g1b2a542 (latest on stable-2.6 branch),
> but I guess/hope that's not the reason for the error :-)
>
> [1]: http://hydra.nixos.org/job/nixos/trunk-combined/nixpkgs.linuxPackages_3_18.lttng-modules.i686-linux
So apparantly this is fixed in master:
http://lists.lttng.org/pipermail/lttng-dev/2015-April/024395.html
Are you planning to backport the fix to stable-2.6? And possibly make
a release? (Speaking as a distro packager here.)
Best regards,
Bj?rn Forsman
next parent reply other threads:[~2015-04-12 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEYzJUH27pYhSZmFEeaCQ7deeH75+GhjrVjdGN6dnyG+DyQhXA@mail.gmail.com>
2015-04-12 13:55 ` Bjørn Forsman [this message]
2015-04-23 21:29 ` Mathieu Desnoyers
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='CAEYzJUGL6Q_o=zESuhhszBKGUCYrTwxBp32xppicQLZa6a4nVg@mail.gmail.com' \
--to=bjorn.forsman@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox