From: Joshua Watt <jpewhacker@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>,
OE-core <openembedded-core@lists.openembedded.org>,
Yocto-mailing-list <yocto@yoctoproject.org>
Subject: Re: GCC 8 hosts
Date: Wed, 25 Apr 2018 08:05:33 -0500 [thread overview]
Message-ID: <1524661533.31562.2.camel@gmail.com> (raw)
In-Reply-To: <CAJTo0LbOsiLq=0Zz=4fPE-A7Q7Ez_XVgqm8CBkSeAu6Bz=myLg@mail.gmail.com>
On Wed, 2018-04-25 at 13:11 +0100, Burton, Ross wrote:
> Hi,
>
> Just thought I'd say that GCC 8 is going to start appearing in the
> wild, I believe the first distro to ship with it will be Fedora 28.
> As usual there are changes in behaviour so there are several
> problems.
> So far I've identified the following issues:
>
> * Python 2 crashes on startup
> * Kernel tools fail to build
> * grub fails to build
> * ovmf fails to build
>
> I've patches locally for all but the ovmf failure (which is a pain
> because the source uses CRLF) so if anyone switches to a GCC 8 host
> before they're merged and wants to help, you know where to find me.
Do you have a branch with the patches somewhere so we can try them out?
>
> Ross
WARNING: multiple messages have this Message-ID (diff)
From: Joshua Watt <jpewhacker@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>,
OE-core <openembedded-core@lists.openembedded.org>,
Yocto-mailing-list <yocto@yoctoproject.org>
Subject: Re: [OE-core] GCC 8 hosts
Date: Wed, 25 Apr 2018 08:05:33 -0500 [thread overview]
Message-ID: <1524661533.31562.2.camel@gmail.com> (raw)
In-Reply-To: <CAJTo0LbOsiLq=0Zz=4fPE-A7Q7Ez_XVgqm8CBkSeAu6Bz=myLg@mail.gmail.com>
On Wed, 2018-04-25 at 13:11 +0100, Burton, Ross wrote:
> Hi,
>
> Just thought I'd say that GCC 8 is going to start appearing in the
> wild, I believe the first distro to ship with it will be Fedora 28.
> As usual there are changes in behaviour so there are several
> problems.
> So far I've identified the following issues:
>
> * Python 2 crashes on startup
> * Kernel tools fail to build
> * grub fails to build
> * ovmf fails to build
>
> I've patches locally for all but the ovmf failure (which is a pain
> because the source uses CRLF) so if anyone switches to a GCC 8 host
> before they're merged and wants to help, you know where to find me.
Do you have a branch with the patches somewhere so we can try them out?
>
> Ross
next prev parent reply other threads:[~2018-04-25 13:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 12:11 GCC 8 hosts Burton, Ross
2018-04-25 13:05 ` Joshua Watt [this message]
2018-04-25 13:05 ` [OE-core] " Joshua Watt
2018-04-25 13:57 ` Burton, Ross
2018-04-25 13:57 ` [OE-core] " Burton, Ross
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=1524661533.31562.2.camel@gmail.com \
--to=jpewhacker@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
--cc=yocto@yoctoproject.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.