All of lore.kernel.org
 help / color / mirror / Atom feed
From: ddu <dengke.du@windriver.com>
To: lttng-dev@lists.lttng.org
Subject: conflicting types for 'trace_signal_generate'
Date: Thu, 31 Jan 2019 14:49:45 +0800	[thread overview]
Message-ID: <39d9fb3a-4613-7e77-b586-9df3f811d294__17755.5857620732$1548921634$gmane$org@windriver.com> (raw)

Hi all

Yocto branch: master

lttng-modules: 2.10.8

kernel: 5.0-rc

------------------------------------------------------------------------------------

  /buildarea1/ddu/wrp/1019/lttng/build/workspace/sources/lttng-modules/probes/../probes/lttng-tracepoint-event-impl.h:143:6: error: conflicting types for 'trace_signal_genera     te'
   void trace_##_name(_proto);
        ^~~~~~
  /buildarea1/ddu/wrp/1019/lttng/build/workspace/sources/lttng-modules/probes/../probes/lttng-tracepoint-event-impl.h:55:2: note: in expansion of macro 'LTTNG_TRACEPOINT_EVEN T_INSTANCE_MAP'
    LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), 
PARAMS(args))
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  /buildarea1/ddu/wrp/1019/lttng/build/workspace/sources/lttng-modules/probes/../probes/lttng-tracepoint-event-impl.h:97:2: note: in expansion of macro 'LTTNG_TRACEPOINT_EVEN     T_MAP'
    LTTNG_TRACEPOINT_EVENT_MAP(name, name,    \
    ^~~~~~~~~~~~~~~~~~~~~~~~~~
  /buildarea1/ddu/wrp/1019/lttng/build/workspace/sources/lttng-modules/probes/../instrumentation/events/lttng-module/signal.h:53:1: note: in expansion of macro 'LTTNG_TRACEPO     INT_EVENT'
   LTTNG_TRACEPOINT_EVENT(signal_generate,
   ^~~~~~~~~~~~~~~~~~~~~~
  In file included from 
/buildarea1/ddu/wrp/1019/lttng/build/tmp-glibc/work-shared/qemux86-64/kernel-source/include/trace/events/signal.h:10,
                   from 
/buildarea1/ddu/wrp/1019/lttng/build/workspace/sources/lttng-modules/probes/lttng-probe-signal.c:30:
  /buildarea1/ddu/wrp/1019/lttng/build/tmp-glibc/work-shared/qemux86-64/kernel-source/include/linux/tracepoint.h:235:21: note: previous definition of 'trace_signal_generate'      was here
    static inline void trace_##name(proto)    \
                       ^~~~~~
  /buildarea1/ddu/wrp/1019/lttng/build/tmp-glibc/work-shared/qemux86-64/kernel-source/include/linux/tracepoint.h:398:2: note: in expansion of macro '__DECLARE_TRACE'
    __DECLARE_TRACE(name, PARAMS(proto), PARAMS(args),  \
    ^~~~~~~~~~~~~~~
  /buildarea1/ddu/wrp/1019/lttng/build/tmp-glibc/work-shared/qemux86-64/kernel-source/include/linux/tracepoint.h:534:2: note: in expansion of macro 'DECLARE_TRACE'
    DECLARE_TRACE(name, PARAMS(proto), PARAMS(args))
    ^~~~~~~~~~~~~
  /buildarea1/ddu/wrp/1019/lttng/build/tmp-glibc/work-shared/qemux86-64/kernel-source/include/trace/events/signal.h:50:1: note: in expansion of macro 'TRACE_EVENT'
   TRACE_EVENT(signal_generate,
   ^~~~~~~~~~~
------------------------------------------------------------------------------------

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

             reply	other threads:[~2019-01-31  8:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31  6:49 ddu [this message]
     [not found] <39d9fb3a-4613-7e77-b586-9df3f811d294@windriver.com>
2019-01-31 16:06 ` conflicting types for 'trace_signal_generate' Mathieu Desnoyers
     [not found] ` <79761919.445.1548950798791.JavaMail.zimbra@efficios.com>
2019-02-01  6:57   ` ddu

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='39d9fb3a-4613-7e77-b586-9df3f811d294__17755.5857620732$1548921634$gmane$org@windriver.com' \
    --to=dengke.du@windriver.com \
    --cc=lttng-dev@lists.lttng.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 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.