From: Szymon Janc <szymon.janc@codecoup.pl>
To: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"Gix, Brian" <brian.gix@intel.com>
Cc: "luiz.dentz@gmail.com" <luiz.dentz@gmail.com>,
"marcel@holtmann.org" <marcel@holtmann.org>
Subject: Re: Build errors under Fedora 32 beta distro / GCC 10.0.1
Date: Mon, 20 Apr 2020 14:08:30 +0200 [thread overview]
Message-ID: <2525599.mvXUDI8C0e@ix> (raw)
In-Reply-To: <5f5cc8a0b25cb7a2a289f83cfbf42b2f86e36f28.camel@intel.com>
Hi Brian,
On Friday, 17 April 2020 20:44:30 CEST Gix, Brian wrote:
> Compiling BlueZ using GCC 10.0.1, which is the standard version for Fedora
> 32 distro:
> $ gcc --version
> gcc (GCC) 10.0.1 20200328 (Red Hat 10.0.1-0.11)
> Copyright (C) 2020 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> This is just a snippet of the top of the error log:
I've just sent patches for this and few other errors reported by GCC 10.
--
pozdrawiam
Szymon Janc
prev parent reply other threads:[~2020-04-20 12:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 18:44 Build errors under Fedora 32 beta distro / GCC 10.0.1 Gix, Brian
2020-04-20 12:08 ` Szymon Janc [this message]
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=2525599.mvXUDI8C0e@ix \
--to=szymon.janc@codecoup.pl \
--cc=brian.gix@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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.