From: Trevor Woerner <twoerner@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-browser][PATCH 1/3] chromium: Allow to build in Debug mode.
Date: Tue, 15 Sep 2015 11:03:22 -0400 [thread overview]
Message-ID: <55F8333A.9000007@gmail.com> (raw)
In-Reply-To: <1442321402-22469-2-git-send-email-clopez@igalia.com>
On 09/15/15 08:50, Carlos Alberto Lopez Perez wrote:
> * Add also a patch that workarounds a build error when building
> in Debug mode and using GCC. This patch has no effect when
> building in Release mode because is guarded within ifdef(debug)
> blocks.
>
> Signed-off-by: Carlos Alberto Lopez Perez <clopez@igalia.com>
> ---
> recipes-browser/chromium/chromium.inc | 4 ++-
> .../fix-build-error-with-GCC-in-Debug-mode.patch | 32 ++++++++++++++++++++++
> recipes-browser/chromium/chromium_40.0.2214.91.bb | 1 +
> 3 files changed, 36 insertions(+), 1 deletion(-)
> create mode 100644 recipes-browser/chromium/chromium/chromium-40/fix-build-error-with-GCC-in-Debug-mode.patch
Does the above patch need an upstream-status tag?
next prev parent reply other threads:[~2015-09-15 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 12:49 [meta-browser][PATCH 0/3] chromium: make the build type configurable Carlos Alberto Lopez Perez
2015-09-15 12:50 ` [meta-browser][PATCH 1/3] chromium: Allow to build in Debug mode Carlos Alberto Lopez Perez
2015-09-15 15:03 ` Trevor Woerner [this message]
2015-09-15 17:00 ` Khem Raj
2015-09-16 14:07 ` Carlos Alberto Lopez Perez
2015-09-15 12:50 ` [meta-browser][PATCH 2/3] chromium: Clean the definitions of some ozone-wayland variables Carlos Alberto Lopez Perez
2015-09-15 12:50 ` [meta-browser][PATCH 3/3] chromium: Rework the evaluation of the Wayland feature Carlos Alberto Lopez Perez
2015-09-15 16:56 ` Khem Raj
2015-09-16 14:08 ` Carlos Alberto Lopez Perez
2015-09-16 20:14 ` 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=55F8333A.9000007@gmail.com \
--to=twoerner@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 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.