From: akuster808 <akuster808@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [krogoth][PATCH 1/8] pkgconfig: Fix build with gcc-6
Date: Fri, 15 Jul 2016 07:27:15 -0700 [thread overview]
Message-ID: <5788F2C3.800@gmail.com> (raw)
In-Reply-To: <CAJTo0LY8M1k=XoHYYfTXo9uvCcBgqU6C7mttOvPdeqyR1_XbZw@mail.gmail.com>
On 07/15/2016 07:08 AM, Burton, Ross wrote:
> On 15 July 2016 at 14:53, akuster808 <akuster808@gmail.com> wrote:
>
>> So this is the host gcc not the one in OE?
>>
>
> Yes, the situation was host with gcc6 building krogoth.
Thanks. After looking further down the queue I found the PATCH 0/8 and
it explained.
The original master commits are cryptic on which GCC 6 has the issue.
thanks,
- Armin
>
> Ross
>
next prev parent reply other threads:[~2016-07-15 14:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 1:49 [krogoth][PATCH 0/8] Fixes for gcc-6 (Fedora-24) Tim Orling
2016-07-15 1:49 ` [krogoth][PATCH 1/8] pkgconfig: Fix build with gcc-6 Tim Orling
2016-07-15 13:53 ` akuster808
2016-07-15 14:08 ` Burton, Ross
2016-07-15 14:27 ` akuster808 [this message]
2016-07-15 17:32 ` Tim Orling
2016-07-15 1:49 ` [krogoth][PATCH 2/8] elfutils-0.148: Fix build with gcc6 Tim Orling
2016-07-15 1:49 ` [krogoth][PATCH 3/8] elfutils: Fix build for gcc-6 Tim Orling
2016-07-15 1:49 ` [krogoth][PATCH 4/8] rpm: Fix build with gcc6 Tim Orling
2016-07-15 1:49 ` [krogoth][PATCH 5/8] glib-2.0: Ignore useless warning found with gcc-6 Tim Orling
2016-07-15 1:49 ` [krogoth][PATCH 6/8] binutils: disable werror on native build Tim Orling
2016-07-15 3:26 ` Khem Raj
2016-07-15 3:58 ` Tim Orling
2016-07-15 4:52 ` Khem Raj
2016-07-15 1:49 ` [krogoth][PATCH 7/8] openjade-native: work around bug exposed by GCC 6 Tim Orling
2016-07-15 1:49 ` [krogoth][PATCH 8/8] gcc-5.3: fix build for gcc-6 Tim Orling
2016-07-15 14:16 ` [krogoth][PATCH 0/8] Fixes for gcc-6 (Fedora-24) akuster808
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=5788F2C3.800@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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