From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: nss: update to 3.49.2
Date: Thu, 30 Jan 2020 16:43:37 +0100 [thread overview]
Message-ID: <20200130154337.d-Aq1TKuolEfpVbwERmobMJ4VWpKxHKksUVt78YmbHI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18626@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
There's a merged pull request on the void-packages repository
nss: update to 3.49.2
https://github.com/void-linux/void-packages/pull/18626
Description:
Had to remove `arm32.patch` because the `patch` program rejected it.
Line 783 to 790 of `masterdir/builddir/nss-3.49.2/nss/lib/freebl/Makefile` is:
```
ifeq ($(CPU_ARCH),arm)
# When the compiler uses the softfloat ABI, we want to use the compatible softfp ABI when
# enabling NEON for these objects.
# Confusingly, __SOFTFP__ is the name of the define for the softfloat ABI, not for the softfp ABI.
USES_SOFTFLOAT_ABI := $(shell $(CC) -o - -E -dM - $(CFLAGS) < /dev/null | grep __SOFTFP__ > /dev/null && echo 1)
$(OBJDIR)/$(PROG_PREFIX)aes-armv8$(OBJ_SUFFIX): CFLAGS += -march=armv8-a -mfpu=crypto-neon-fp-armv8$(if $(USES_SOFTFLOAT_ABI), -mfloat-abi=softfp)
$(OBJDIR)/$(PROG_PREFIX)gcm-arm32-neon$(OBJ_SUFFIX): CFLAGS += -mfpu=neon$(if $(USES_SOFTFLOAT_ABI), -mfloat-abi=softfp)
endif
```
As such, I think that `arm32.patch` is no longer needed. Please correct me if I am wrong.
prev parent reply other threads:[~2020-01-30 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 6:52 [PR PATCH] [WIP] " voidlinux-github
2020-01-30 10:39 ` voidlinux-github
2020-01-30 10:44 ` voidlinux-github
2020-01-30 15:43 ` voidlinux-github [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=20200130154337.d-Aq1TKuolEfpVbwERmobMJ4VWpKxHKksUVt78YmbHI@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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 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 NNTP newsgroup(s).