From: Trevor Woerner <twoerner@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: chromium 40.0.2214.91 doesn't like gcc5.3
Date: Wed, 30 Dec 2015 11:53:49 -0500 [thread overview]
Message-ID: <56840C1D.7080800@gmail.com> (raw)
In-Reply-To: <20151230165246.GE2263@jama>
On 12/30/15 11:52, Martin Jansa wrote:
> On Wed, Dec 30, 2015 at 01:18:48AM -0500, Trevor Woerner wrote:
>> I noticed the recent gcc update from 5.2 to 5.3 in openembedded-core
>> seems to cause meta-browser's chromium build to fail with more warnings
>> being treated as errors. My MACHINE is intel-corei7-64, but I'm guessing
>> this probably happens on other architectures too.
>>
>> Is anyone looking at this?
>>
>> Is there any talk about this upstream?
> It was fixed for gcc-5.2 with this patch:
> http://lists.openembedded.org/pipermail/openembedded-devel/2015-November/104327.html
>
> I'm surprised that it doesn't work with 5.3, but I can confirm the same
> failures in latest "bitbake world" builds.
I agree, I was surprised too. That's why I CC'ed Max on my email since I
figured he'd be best positioned to comment on this :-)
next prev parent reply other threads:[~2015-12-30 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 6:18 chromium 40.0.2214.91 doesn't like gcc5.3 Trevor Woerner
2015-12-30 15:26 ` Max Krummenacher
2015-12-30 15:55 ` Trevor Woerner
2015-12-30 17:55 ` Trevor Woerner
2015-12-30 16:52 ` Martin Jansa
2015-12-30 16:53 ` Trevor Woerner [this message]
2015-12-30 18:04 ` Khem Raj
2015-12-30 19:38 ` Trevor Woerner
2015-12-30 20:54 ` Khem Raj
2016-01-01 3:10 ` Trevor Woerner
2016-01-01 7:07 ` 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=56840C1D.7080800@gmail.com \
--to=twoerner@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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.