All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: Max Krummenacher <max.oss.09@gmail.com>,
	"openembedded-devel@lists.openembedded.org"
	<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 10:55:02 -0500	[thread overview]
Message-ID: <5683FE56.8080208@gmail.com> (raw)
In-Reply-To: <1451489161.2176.12.camel@gmail.com>

Hi Max,

On 12/30/15 10:26, Max Krummenacher wrote:
> Hi Trevor
>
> Am Mittwoch, den 30.12.2015, 01:18 -0500 schrieb Trevor Woerner:
>> 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.
> I tried to build master with GCC 5.3 for an armv7 target just now.
> The same error that you see pops up.

Thanks for trying this with a different MACHINE and confirming it's
there too.

> I propose to lower the strict-overflow to a warning again to get
> rid of this errors once and for all.
>
> The following made the build work for me:

Is there any way to set the flags per compilation unit, or
per-directory? According to the source layout, the problem is in a file
identified as "third party". In that case it's understandable that
someone else's code has an issue. But it would be nice to keep this flag
for the core chromium build (since that's what the chromium developers set).

Maybe a newer version already has a fix for this in the code (which
would be a better place to fix an issue such as this)?

Best regards,
    Trevor


  reply	other threads:[~2015-12-30 15:55 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 [this message]
2015-12-30 17:55   ` Trevor Woerner
2015-12-30 16:52 ` Martin Jansa
2015-12-30 16:53   ` Trevor Woerner
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=5683FE56.8080208@gmail.com \
    --to=twoerner@gmail.com \
    --cc=max.oss.09@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.