unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 36930@debbugs.gnu.org
Subject: bug#36930: NSS 3.45 fails to build on armhf-linux
Date: Mon, 05 Aug 2019 11:52:22 -0400	[thread overview]
Message-ID: <87sgqfa9ta.fsf@netris.org> (raw)
In-Reply-To: <878ss73it7.fsf@devup.no> (Marius Bakke's message of "Mon, 05 Aug 2019 14:20:20 +0200")

Hi Marius,

Marius Bakke <mbakke@fastmail.com> writes:

> On armhf-linux, 'nss' fails early in the build process due to an
> undefined reference to "PR_Assert":
>
> https://ci.guix.gnu.org/log/5cqmmjd9a8h05l8y352z1pq4mlyd6w21-nss-3.45
>
> This is almost certainly because of this upstream commit, which swaps
> out the curve25519 implementation for 32-bit ARM systems:
>
> https://hg.mozilla.org/projects/nss/rev/7b749ff400db3ecab87f394c091ea0831254e674
>
> There is some discussion about it in this ticket:
> https://bugzilla.mozilla.org/show_bug.cgi?id=1550579
>
> I don't know how all those people were able to benchmark the change.
> Perhaps we are missing something in our build flags?
>
> With NSS 3.45 now in the 'master' branch, we should fix this issue
> quickly as armhf users are currently unable to update their systems.
>
> I filed an upstream ticket here, but no response yet:
> https://bugzilla.mozilla.org/show_bug.cgi?id=1571316

For now, we could simply revert my commit that updates NSS to 3.45.
Although I mentioned in the commit log that it fixed some CVEs, I later
discovered that 3.44.1 includes fixes for the same CVEs.  NSS 3.44.1 was
the version of NSS in 'master' before my commit.

       Mark

  reply	other threads:[~2019-08-05 15:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-05 12:20 bug#36930: NSS 3.45 fails to build on armhf-linux Marius Bakke
2019-08-05 15:52 ` Mark H Weaver [this message]
2019-08-05 16:51   ` Mark H Weaver
2019-08-05 17:46     ` Marius Bakke
2020-04-07 12:33 ` Marius Bakke

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sgqfa9ta.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=36930@debbugs.gnu.org \
    --cc=mbakke@fastmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).