From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 13/17] nss: update to 3.21
Date: Tue, 29 Dec 2015 17:54:29 +0200 [thread overview]
Message-ID: <5682ACB5.4060005@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LaCS-MeOUOUiBPNbhuBry3b5fo-5eR-JtREigUyav_39g@mail.gmail.com>
On 12/23/2015 03:11 PM, Burton, Ross wrote:
>
> On 17 December 2015 at 15:08, Alexander Kanavin
> <alexander.kanavin@linux.intel.com
> <mailto:alexander.kanavin@linux.intel.com>> wrote:
>
> meta/recipes-support/nss/{nss_3.19.2.bb <http://nss_3.19.2.bb> =>
> nss_3.21.bb <http://nss_3.21.bb>} | 6 +++---
>
>
> Failed on the autobuilder in a number of interesting ways:
The first two failures are because unit tests are now enabled by default
in the new release, upstream is using C++11 for them and didn't test
well that they actually build in various environments:
https://bugzilla.mozilla.org/show_bug.cgi?id=1225377
The tests can be skipped by setting 'export NSS_DISABLE_GTESTS=1' in the
recipe (both compile and install steps).
The third failure is probably a gcc 4.8 issue on opensuse 13.1. I can't
reproduce it here. Would you be able to develop a fix? Or we can try
again when upstream makes a new release.
Alex
next prev parent reply other threads:[~2015-12-29 15:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 15:08 [PATCH 00/17] Recipe version updates Alexander Kanavin
2015-12-17 15:08 ` [PATCH 01/17] cryptodev: update to 1.8 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 02/17] gptfdisk: update to 1.0.1 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 03/17] ifupdown: update to 0.8.2 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 04/17] pytnon-pexpect: update to 4.0.1 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 05/17] python3-pip: update to 7.1.2 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 06/17] trace-cmd: update to 2.6 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 07/17] liburcu: update to 0.9.1 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 08/17] msmtp: update to 1.6.3 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 09/17] libassuan: update to 2.4.2 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 10/17] tiff: update to 4.0.6 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 11/17] lighttpd: update to 1.4.38 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 12/17] kexec-tools: update to 2.0.11 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 13/17] nss: update to 3.21 Alexander Kanavin
2015-12-23 13:11 ` Burton, Ross
2015-12-29 15:54 ` Alexander Kanavin [this message]
2016-01-18 18:00 ` alexander.kanavin
2016-01-18 17:17 ` Richard Purdie
2015-12-17 15:08 ` [PATCH 14/17] iso-codes: update to 3.63 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 15/17] btrfs-tools: update to 4.3.1 Alexander Kanavin
2015-12-17 15:08 ` [PATCH 16/17] icu: fix upstream version check Alexander Kanavin
2015-12-17 15:08 ` [PATCH 17/17] mobile-broadband-provider-info: update to tagged release 20151214 Alexander Kanavin
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=5682ACB5.4060005@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.