• Rather than declare a new variable to disable native compilation of FreeBSD ports, reuse the existing variable, native-comp-jit-compilation, which controls native compilation of all third-party elisp.
• Tweak documentation
• Update pkg-message

In D56001#1289189, @rhurlin wrote:

Thanks for this overhaul of emacs infrastructure.

Based on these patches, I rebuilt and installed editors/emacs and math/ess; I didn't need to apply the script from UPDATING.
The port math/ess works as expected with the patches and is actually much faster with long R scripts ;)

BTW and a bit off-topic: Is it still necessary for editors/emacs to set the following option to GCC version 13?

OPTION NATIVECOMP_USE= GCC=13

In D56001#1288640, @mce wrote:

This is a patch for japanese/ddskk.

• Incorporate improvements from @mce
  • Patch the build rather than delete .elc from STAGEDIR in a post-install target

• Set @tijl as maintainer of devel/gettext-po-mode
• japanese/navi2ch/pkg-plist: Uses PLIST_SUB variable

• Change an instance of EMACS_VERSION_SITE_LISPDIR to EMACS_VERSION_LISPDIR in textproc/yaml.el; this was accidentally missed earlier

• DEFAULT_VERSIONS+=emacs=... now sets the Emacs port and flavor used for USES=emacs:build ports
• Fix a whitespace error noted by @mandree
• Add a function to clean up stale eln-cache subdirectories left by previous Emacs builds

@mandree, I fixed one double blank line in UPDATING, but as far as I can see, all the others are false positives in generated patches such as audio/emms/files/patch-Makefile. You can see the space before tab complaints are just the diff context markers before a TAB. In these cases, because those lines were unchanged, there is a space instead of a + or -.

Does this approach work for your use case?Hi @freebsd_dev.thsi.be,

Rebase and fix merge conflicts after @mce's refactoring of japanese/navi2ch

• Fix a regexp issue in default.el.in. When I switched some regexps to be anchored at the end of string rather than end of line, I switched, e.g., "\\.elc$" to "\\.el\\" when I should have done "\\.el\\'".

I moved these changes to D56116. It's better to commit this in one go.

• Regexps like \\.el$ should be anchored at the end of the string rather the end of the line (\\.el\\).
• Move the elsip port changes from D56116 to here; it's better to make this one commit.

Tweak some pkg-messages:

Load all autoloads files installed by FreeBSD elisp ports. This mirrors what package.el does for ELPA packages, ensuring that autoloaded functions are available without requiring users to explicitly load each package.

• Only put the variable definitions in site-start.el, and the rest of the startup code in default.el. This separation makes it easier for users to selectively disable native or byte compilation.
• Rebase.

• Add support for byte compilation
• Add variables to allow users to easily disable either byte compilation or native compilation

I thought of this as an addendum to your work, and, ideally, we reviewers should have caught it in https://reviews.freebsd.org/D55938. Since you're busy tackling the arm32 and powerpc64 stuff, I'll take care of this.

I responded to the commit mail, but it might be helpful to include this in the review for posterity.

Minor change to print/pdf-tools

Guard native-compile-async in site-start.el so it only runs in interactive sessions, not batch mode.

Fix a few build issues

https://reviews.freebsd.org/D56051

• Move elisp port changes to a separate reivew.
• Only set EMACS_CMD, EMACS_MAJOR_VER, and EMACS_VER when the build argument is supplied.

In D56001#1282321, @guest-patmaddox wrote:

I understand the motivation for this. I don't understand auto compiling on behalf of the user.

Given those concerns, native compilation is the right path for users who care about performance.

Seems like we should just ship the elisp and let the user configure Emacs to native compile if they want? Which I'm pretty sure it does by default anyway.

The build was failing because the cmake_install.cmake step for vpp-api/python was calling pip install to download and install some things from PyPi.

• Remove an old refernce to EMACS_LIBDIR_WITH_VER in emacs.mk
• Tweak variable order in emacs.mk

Incorporate necessary changes to editors/emacs

This is still in the design stage, so I haven't:

• made the changes needed for editors/emacs
• made the changes needed to most USES=emacs ports

The build looks good on 16amd64: https://pkg.ftfl.ca/build.html?mastername=16amd64-default&build=2026-03-19_12h15m13s

Commited in 16cef5f7a65588def71db4fdfa961f959847e3b6.

Commited in 16cef5f7a65588def71db4fdfa961f959847e3b6.

Committed in e6083790f217ba7f89cd2957922bd45e35466359.

Committed in e6083790f217ba7f89cd2957922bd45e35466359.

Looks good to me. portclippy and portfmt have some suggested formatting changes in case you want to incorporate them at some point.

All the changes are now annotated. @glebius's changes to pcap-bpf.c were merged upstream in https://github.com/the-tcpdump-group/libpcap/commit/ea5317adaf0e4e308543fbd66977f89344f9ef7f, so our local changes should go away with the next pcacp update.

Add more context to the diff.

Thanks. Looks good for sysutils/tmux and sysutils/arc_summary.

In D55545#1272751, @emaste wrote:

ssh has a similar issue.

Whould #define SIZEOF_TIME_T sizeof(time_t) work?

Incorporate feedback (via IRC) from kevans about how to define SIZEOF_TIME_T. It's also 64-bit on all 32-bit platforms except i386.

Ooops. I was trying to fast-track ivy after a discussion on IRC, and I hadn't refreshed the page to see that this was already approved.

This update was straightforward and only required manual changes to: