All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Joshua Lock <joshua.g.lock@intel.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: Thu, 6 Apr 2017 06:50:47 -0700	[thread overview]
Message-ID: <CAMKF1sq7VfdNAJG60Ls6aoQOW2YvHztNqk_z8JwVWO=m1LpkKQ@mail.gmail.com> (raw)
In-Reply-To: <cover.1491484515.git.joshua.g.lock@intel.com>

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.

>
> 1. https://fedoraproject.org/wiki/Changes/GCC7
> 2. https://fedoraproject.org/wiki/Changes/pkgconf_as_system_pkg-config_implementation

I think we should think about making pkgconf as default too for OE in
next release cycle.

>
> The following changes since commit 633ad6c9f436f5d2b6ee1a005b697661a054a394:
>
>   oeqa/runtime/utils/targetbuildproject: use parent classes defaults tmpdir (2017-04-06 10:13:39 +0100)
>
> are available in the git repository at:
>
>   git://git.yoctoproject.org/poky-contrib joshuagl/fedora26
>   http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=joshuagl/fedora26
>
> Joshua Lock (2):
>   elfutils: fix building elfutils-native with GCC7
>   gcc-6.3: backport fix of check for empty string in ubsan.c
>
>  .../elfutils-0.168/Fix_one_GCC7_warning.patch      | 44 ++++++++++++++++++++++
>  .../elfutils/elfutils-0.168/fallthrough.patch      | 36 ++++++++++++++++++
>  meta/recipes-devtools/elfutils/elfutils_0.168.bb   |  3 ++
>  meta/recipes-devtools/gcc/gcc-6.3.inc              |  1 +
>  .../gcc/gcc-6.3/ubsan-fix-check-empty-string.patch | 28 ++++++++++++++
>  5 files changed, 112 insertions(+)
>  create mode 100644 meta/recipes-devtools/elfutils/elfutils-0.168/Fix_one_GCC7_warning.patch
>  create mode 100644 meta/recipes-devtools/elfutils/elfutils-0.168/fallthrough.patch
>  create mode 100644 meta/recipes-devtools/gcc/gcc-6.3/ubsan-fix-check-empty-string.patch
>
> --
> 2.9.3
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


  parent reply	other threads:[~2017-04-06 13:51 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 ` Khem Raj [this message]
2017-04-07 10:06   ` [PATCH 0/2] Fixes for building on Fedora 26 (Alpha) Joshua Lock
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='CAMKF1sq7VfdNAJG60Ls6aoQOW2YvHztNqk_z8JwVWO=m1LpkKQ@mail.gmail.com' \
    --to=raj.khem@gmail.com \
    --cc=joshua.g.lock@intel.com \
    --cc=openembedded-core@lists.openembedded.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.