From: "Eric Bénard" <eric@eukrea.com>
To: Diego Rondini <diego.ml@zoho.com>
Cc: openembedded-devel@lists.openembedded.org,
Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [meta-browser][PATCH] chromium: Fix build with nss 3.15
Date: Wed, 5 Feb 2014 10:07:34 +0100 [thread overview]
Message-ID: <20140205100734.57360f43@e6520eb> (raw)
In-Reply-To: <1391589897-10063-1-git-send-email-diego.ml@zoho.com>
Hi Diego,
Le Wed, 5 Feb 2014 09:44:57 +0100,
Diego Rondini <diego.ml@zoho.com> a écrit :
> Meta-browser commit 4b7a82273a85802070441e9c510e0891acc482fa broke Chromium build because removal of meta-browser nss 3.13.3 forced build against OE-Core 3.15.1, which is not supported out of the box by Chromium 29.
> This commit backports this patch:
> https://src.chromium.org/viewvc/chrome/trunk/src/net/third_party/nss/ssl/bodge/secitem_array.c?r1=206184&r2=206183&pathrev=206184&diff_format=u
>
> Upstream-Status: Backport of SVN REV 206184
>
> Signed-off-by: Diego Rondini <diego.ml@zoho.com>
patch committed
Thanks
Eric
prev parent reply other threads:[~2014-02-05 9:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 8:44 [meta-browser][PATCH] chromium: Fix build with nss 3.15 Diego Rondini
2014-02-05 9:07 ` Eric Bénard [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=20140205100734.57360f43@e6520eb \
--to=eric@eukrea.com \
--cc=diego.ml@zoho.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox