All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Alberto Lopez Perez <clopez@igalia.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-browser][PATCH 1/3] chromium: Allow to build in Debug mode.
Date: Wed, 16 Sep 2015 16:07:22 +0200	[thread overview]
Message-ID: <55F9779A.8020402@igalia.com> (raw)
In-Reply-To: <CAMKF1srGtU9VS9FHTRsKACHXwJSmTQGVjg25ORom7w=_GM=QWw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]

On 15/09/15 19:00, Khem Raj wrote:
> On Tue, Sep 15, 2015 at 8:03 AM, Trevor Woerner <twoerner@gmail.com> wrote:
>> 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?
> 
> Its not must for meta-broweser, but its good since it adds
> information. We do not have any automatic tracking of patch status
> so if one mentions url for source of patch or any information on where
> patch's status can be asserted at later times is good.
> 

The patch itself includes in the comments at top the URL to the chromium
bugtracker where the issue was reported and the patch forwarded.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

  reply	other threads:[~2015-09-16 14:07 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
2015-09-15 17:00     ` Khem Raj
2015-09-16 14:07       ` Carlos Alberto Lopez Perez [this message]
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=55F9779A.8020402@igalia.com \
    --to=clopez@igalia.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.