From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: is there an actual "compiler-gcc6.h" patch?
Date: Wed, 15 Jun 2016 08:51:11 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1606150849540.25853@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.20.1606150839230.9417@localhost.localdomain>
On Wed, 15 Jun 2016, Robert P. J. Day wrote:
>
> following on a post to the list from back on jun 1:
>
> https://www.mail-archive.com/yocto@yoctoproject.org/msg29568.html
>
> i figured it wouldn't be hard to find the place where that header file
> was added to the master branch for (in this case) the 4.1 kernel, but
> i just checked the git repo, master branch, and i don't see that file
> there, but i see that a patch to add it was submitted back on june 2:
>
> https://github.com/Freescale/meta-fsl-arm/blob/master/recipes-kernel/linux/linux-ls1/Fix-the-compile-issue-under-gcc6.patch
>
> so what is the status of this? am i just reading this incorrectly? or
> doing something wrong?
i do realize that that patch referred to above was for the
meta-fsl-arm repo, i just assumed it would work its way into master in
short order. but i could be totally off-base here.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2016-06-15 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 12:43 is there an actual "compiler-gcc6.h" patch? Robert P. J. Day
2016-06-15 12:51 ` Robert P. J. Day [this message]
2016-06-15 13:12 ` Martin Jansa
2016-06-15 13:15 ` Robert P. J. Day
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=alpine.LFD.2.20.1606150849540.25853@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--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.