linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Subject: Re: [PATCH] trace-cmd: Fix build with gcc-10
Date: Mon, 20 Apr 2020 23:37:17 +0100	[thread overview]
Message-ID: <CADVatmN4Xv00=VvWma9kRwYhsX=jzFn3t8052y1o54srEt6LfQ@mail.gmail.com> (raw)
In-Reply-To: <20200420155320.55d3c3f2@gandalf.local.home>

On Mon, Apr 20, 2020 at 8:53 PM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Mon, 20 Apr 2020 15:43:25 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > On Fri, 17 Apr 2020 21:39:14 +0100
> > Sudip Mukherjee <sudipm.mukherjee@gmail.com> wrote:
> >
> > > The build fails while building with gcc-10 with the error:
> > > multiple definition of `common_type_field'
> >
<snip>
>
> OK, I'll take this patch, and may even enable a -fno-common to find other
> cases of this without having to wait till my distro adds gcc 10 by default.

Thanks Steve. We have gcc-10 in the experimental release of Debian and
I am using that to build. Looks like this was the only one case which
gcc found.


-- 
Regards
Sudip

  reply	other threads:[~2020-04-20 22:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-17 20:39 [PATCH] trace-cmd: Fix build with gcc-10 Sudip Mukherjee
2020-04-20 19:43 ` Steven Rostedt
2020-04-20 19:53   ` Steven Rostedt
2020-04-20 22:37     ` Sudip Mukherjee [this message]
2020-05-08 12:46       ` Sudip Mukherjee
2020-05-08 14:11         ` Steven Rostedt
2020-05-09 18:30           ` Sudip Mukherjee
2020-05-09 18:48             ` Steven Rostedt
2020-05-09 19:11               ` Sudip Mukherjee
2020-05-09 21:12                 ` Steven Rostedt
2020-05-09 23:27                   ` Sudip Mukherjee

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='CADVatmN4Xv00=VvWma9kRwYhsX=jzFn3t8052y1o54srEt6LfQ@mail.gmail.com' \
    --to=sudipm.mukherjee@gmail.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).