security/nss targeting armv7 tries to compile armv8-a source code: nss/lib/freebl/aes-armv8.c
nss/lib/freebl/Makefile has: ifeq ($(CPU_ARCH),arm) $(OBJDIR)/$(PROG_PREFIX)aes-armv8$(OBJ_SUFFIX): CFLAGS += -march=armv8-a -mfpu=crypto-neon-fp-armv8 $(OBJDIR)/$(PROG_PREFIX)gcm-arm32-neon$(OBJ_SUFFIX): CFLAGS += -mfpu=neon endif but targeting -mcpu=cortex-a7 (an armv7) results in the likes of: cc -o FreeBSD15.0_OPT.OBJ/FreeBSD_SINGLE_SHLIB/aes-armv8.o -c -std=c99 -O2 -gline-tables-only -pipe -mcpu=cortex-a7 . . . . -march=armv8-a -mfpu=crypto-neon-fp-armv8 aes-armv8.c cc: warning: ignoring extension 'sha2' because the 'armv7-a' architecture does not support it [-Winvalid-command-line-argument] cc: warning: ignoring extension 'aes' because the 'armv7-a' architecture does not support it [-Winvalid-command-line-argument] aes-armv8.c:14:2: error: "Compiler option is invalid" 14 | #error "Compiler option is invalid" | ^ from nss/lib/freebl/aes-armv8.c: . . . #include "secerr.h" #include "rijndael.h" #if ((defined(__clang__) || \ (defined(__GNUC__) && defined(__GNUC_MINOR__) && \ (__GNUC__ > 4 || (__GNUC__ == 4 && __GNUC_MINOR__ > 8 && \ defined(IS_LITTLE_ENDIAN)) #ifndef __ARM_FEATURE_CRYPTO #error "Compiler option is invalid" #endif #include . . . (The example happens to be for 3.103 .) Seems odd to me to have armv7 targeting have any dependency on armv8 encoded instructions that from well after armv7 was defined. (Even if the goal is to have the processor reject the instructions.) Note: I ran into this trying to see if I could build www/firefox in a armv7 jail on a aarch64 that supports armv7 code. BE_WASM for llvm*'s may be a waste of resources if armv7 based builds are just not going to work. (I do not normally build firefox.) === Mark Millard marklmi at yahoo.com
Re: NordVPN script for FreeBSD
On August 28, 2024 21:15:06 Laurent wrote: That sounds like fun. I'll ping him to see if I can help. Thanks! Appreciated!
Re: ampere2 did not even try to build main-armv7-default: it is only trying to build main-arm64-default
On 2024-08-27 10:34:18 (+0800), Mark Millard wrote: main-arm64-default on ampere2 has started building as of Tue, 27 Aug 2024 01:58:37 GMT. 14609 were queued. So, unless that is stopped, it will likely be days before main-armv7-default would be started. The arm builds are currently scheduled like this: ampere1: - quarterly arm64.aarch64 13.3-RELEASE 133arm64 -a ampere1: - quarterly arm.armv7 releng/13.3 133releng-armv7 -a ampere1: - quarterly arm64.aarch64 14.0-RELEASE 140arm64 -a ampere1: - quarterly arm.armv7 releng/14.0 140releng-armv7 -a ampere2: - default arm64.aarch64 main main-arm64 -a ampere2: - default arm.armv7 main main-armv7 -a ampere3: - default arm64.aarch64 13.3-RELEASE 133arm64 -a ampere3: - default arm.armv7 releng/13.3 133releng-armv7 -a ampere3: - default arm64.aarch64 14.0-RELEASE 140arm64 -a ampere3: - default arm.armv7 releng/14.0 140releng-armv7 -a ampere2 should start building armv7 when it finishes with its current aarch64 build. I'm keeping an eye on this one. I've also got the next set of FreeBSD-CURRENT builds ready to upgrade it when it goes idle. Philip
Newer eclipse port 4.32 (5) - working
Hello ALL, So after hours of struggling I got a manual installation and a port installation for eclipse 4.32 on FreeBSD working. Maybe not everything is the best solution, but at the end it worked (in a jail) - till the installation. For more detail please have a look on my gtihub repository - there is more description https://github.com/NorbertXYZ/eclipse/ It would be nice to get an answer what to do next? Maybe I would take the maintainership of the "old" eclipse port, which is "only" version 4.24... All the best from Germany, Norbert -- I love penguins at the south pole, windows in my house and apples on my tree, but not in my computer :)
Re: Newer eclipse port 4.32 (5) - working
Hi! > So after hours of struggling I got a manual installation and a port > installation for eclipse 4.32 on FreeBSD working. Maybe not everything > is the best solution, but at the end it worked (in a jail) - till the > installation. > > For more detail please have a look on my gtihub repository - there is > more description > > https://github.com/NorbertXYZ/eclipse/ > > It would be nice to get an answer what to do next? Submit the patch via bugs.freebsd.org, and let someone testbuild and probably test-run on the relevant platforms. The old maintainer will be asked if he approves (which I assume that he will do), and then the patch will be applied and the port updated, probably with you as the maintainer. -- p...@freebsd.org +49 171 3101372 Now what ?
Re: www/chromium-128.0.6613.84 build failure (amd64; poudriere)
On Wed, Aug 28, 2024 at 07:19:54AM -0700, Cy Schubert wrote: > I should have checked ports-committers first. Looks like the fix went in > this morning. > Confirmed: after updating my ports tree (in my case, to main-n675360-efd8eb280e0b), I was able to (eventually!) build chromium-128.0.6613.84.pkg in a stable/14, amd64 environment. Peace, david -- David H. Wolfskill da...@catwhisker.org Restricting bodily autonomy is a mark of autocracy, not conservatism. See https://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
Unmaintained FreeBSD ports which are out of date
Dear port maintainers, The portscout new distfile checker has detected that one or more unmaintained 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. Please consider also adopting this port. If any ports have already been updated, you can safely ignore the entry. An e-mail will not be sent again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ audio/re| 3.14.0 | v3.15.0 +-+ benchmarks/perftest | 4.5-0.17| 24.07.0-0.44 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Reported by:portscout!
