emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#36930: closed (NSS 3.45 fails to build on armhf-linux)


From: GNU bug Tracking System
Subject: bug#36930: closed (NSS 3.45 fails to build on armhf-linux)
Date: Tue, 07 Apr 2020 12:34:01 +0000

Your message dated Tue, 07 Apr 2020 14:33:49 +0200
with message-id <address@hidden>
and subject line Re: bug#36930: NSS 3.45 fails to build on armhf-linux
has caused the debbugs.gnu.org bug report #36930,
regarding NSS 3.45 fails to build on armhf-linux
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
36930: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=36930
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: NSS 3.45 fails to build on armhf-linux Date: Mon, 05 Aug 2019 14:20:20 +0200 User-agent: Notmuch/0.29.1 (https://notmuchmail.org) Emacs/26.2 (x86_64-pc-linux-gnu)
Hello,

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

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- Subject: Re: bug#36930: NSS 3.45 fails to build on armhf-linux Date: Tue, 07 Apr 2020 14:33:49 +0200
This was fixed a while back, closing.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]