From: akuster808 <akuster808@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 00/64] Krogoth-next patches under consideration
Date: Thu, 4 Aug 2016 11:41:54 -0700 [thread overview]
Message-ID: <57A38C72.6040601@gmail.com> (raw)
In-Reply-To: <nnur0j$tp2$1@blaine.gmane.org>
On 08/04/2016 12:31 AM, Koen Kooi wrote:
> Op 02-08-16 om 16:07 schreef Armin Kuster:
>> Most GCC 6 fixed backported. A few packages where updated as they where mostly
>> bug fixes and I noted addition reasons within the commits.
>>
>> I am running builds now. please comment if there is any feedback or missed something.. I hope to have a formal request out by this weekend.
>>
>>
>
>> tvheadend: add CFLAG to ignore misleading indentations
>> geis: add CFLAG to ignore misleading indentations
>> fwts: add CFLAG to ignore misleading indentations
>
> Won't this break building with gcc 4.x and 5.x?
Have not seen any issues with 5.x but let be double check. I would
assume that would have broken in master too since it has gcc 5.3. Have
not checked 4.x.
thanks for reviewing.
- armin
>
prev parent reply other threads:[~2016-08-04 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 14:07 [PATCH 00/64] Krogoth-next patches under consideration Armin Kuster
2016-08-04 7:31 ` Koen Kooi
2016-08-04 18:41 ` akuster808 [this message]
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=57A38C72.6040601@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox