> Mark Millard writes:
>
> > For some reason security/nss tried to build "-march=armv8-a
> > -mfpu=crypto-neon-fp-armv8 aes-armv8.c"
> > material when targeting armv7 (cortex-a7). This did not go well . . .
>
> ARMv8 isn't limited to 64-bit mode. NSS 3.47 builds fine on 12.0 armv7, see
> http:/
Mark Millard writes:
> For some reason security/nss tried to build "-march=armv8-a
> -mfpu=crypto-neon-fp-armv8 aes-armv8.c"
> material when targeting armv7 (cortex-a7). This did not go well . . .
ARMv8 isn't limited to 64-bit mode. NSS 3.47 builds fine on 12.0 armv7, see
http://www.ipv6proxy.n
For some reason security/nss tried to build "-march=armv8-a
-mfpu=crypto-neon-fp-armv8 aes-armv8.c"
material when targeting armv7 (cortex-a7). This did not go well . . .
/nxb-bin/usr/bin/cc -o FreeBSD13.0_OPT.OBJ/FreeBSD_SINGLE_SHLIB/aes-armv8.o -c
-O2 -pipe -mcpu=cortex-a7 -I/usr/local/include
On Fri, 25 Oct 2019 04:05:34 +0200, Tatsuki Makino
wrote:
Can it be solved with USE_PYTHON=concurrent and FLAVOR?
I don't know. If I look at the previous attempts to use flavors. It seems
hard to keep it backwards compatible. But not all patches of all efforts
are available via the PRs.
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you
