From: Joshua Lock <joshua.g.lock@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] Fixes for building on Fedora 26 (Alpha)
Date: Fri, 07 Apr 2017 11:06:55 +0100 [thread overview]
Message-ID: <1491559615.3478.1.camel@linux.intel.com> (raw)
In-Reply-To: <CAMKF1sq7VfdNAJG60Ls6aoQOW2YvHztNqk_z8JwVWO=m1LpkKQ@mail.gmail.com>
On Thu, 2017-04-06 at 06:50 -0700, Khem Raj wrote:
> On Thu, Apr 6, 2017 at 6:23 AM, Joshua Lock <joshua.g.lock@intel.com>
> wrote:
> > As Fedora 26 has a new gcc [1] and a new system pkg-config
> > implementation [2] I
> > wanted to do some testing on that host OS so that we might be able
> > to get some
> > fixes in before Pyro/2.3 is released.
> >
> > The following series were the only changes required to start
> > building (I have
> > tested core-image-minimal, core-image-base and core-image-sato) on
> > Fedora 26.
>
> gcc patch looks fine to me.
Thanks for the review.
> >
> > 1. https://fedoraproject.org/wiki/Changes/GCC7
> > 2. https://fedoraproject.org/wiki/Changes/pkgconf_as_system_pkg-con
> > fig_implementation
>
> I think we should think about making pkgconf as default too for OE in
> next release cycle.
I've filed that as a 2.4 enhancement bug:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=11308
Joshua
next prev parent reply other threads:[~2017-04-07 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 13:23 [PATCH 0/2] Fixes for building on Fedora 26 (Alpha) Joshua Lock
2017-04-06 13:23 ` [PATCH 1/2] elfutils: fix building elfutils-native with GCC7 Joshua Lock
2017-04-06 13:23 ` [PATCH 2/2] gcc-6.3: backport fix of check for empty string in ubsan.c Joshua Lock
2017-04-06 13:50 ` [PATCH 0/2] Fixes for building on Fedora 26 (Alpha) Khem Raj
2017-04-07 10:06 ` Joshua Lock [this message]
2017-04-07 14:02 ` Christopher Larson
2017-04-07 14:23 ` Khem Raj
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=1491559615.3478.1.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@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 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.