FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=main 2026-04-08T07:10:26Z 2026-04-08T07:10:26Z Muhammad Moinur Rahman bofh@FreeBSD.org 2026-04-07T18:27:20Z urn:sha1:a71fea51cecfe3bb70247ad62668e380e0f069ad Enable macros and includes by default as this is breaking package building on HEAD. libucl 0.9.3 by default changed the behavior of includes and macros. These were previously enabled but it switched to disabled which breaks the package building in HEAD. This is a temporary workaround for now to fix the package building specially for releng/15.0. This might be reverted post EOL of 15.0 in the coming months. Reported by: ivy Fixes: abda442d92fd ("contrib/libucl: Import libucl 0.9.3") Tested by: ivy Approved by: ivy, kevans Differential Revision: https://reviews.freebsd.org/D56294 2026-04-03T11:53:18Z Muhammad Moinur Rahman bofh@FreeBSD.org 2026-04-03T11:53:18Z urn:sha1:abda442d92fdbadcf81c79bc9ddba001d133c429 Differential Revision: https://reviews.freebsd.org/D54583 Approved by: bapt MFC after: 3 days Changelog: https://github.com/vstakhov/libucl/releases/tag/0.9.3 2025-10-04T02:16:51Z Kyle Evans kevans@FreeBSD.org 2025-10-04T02:16:51Z urn:sha1:151bd3516b541823b16793460d73916e63d2b9c1 This version builds every module into the flua binary itself, since all of the bootstrap tools are built -DNO_SHARED. As a result, we also cannot dlsym(), so we can't really discover the names of our newly builtin modules. Instead, just build out a linker set with all of our luaopen_*() functions to register everything up-front. Building in all of the modules isn't strictly necessary, but it means that we have an example of how to add a bootstrap module everywhere you go and one doesn't need to consider whether bootstrap flua can use a module when writing scripts. On my build machine, the consequence on our binary size is an increase from around 1.6M -> 1.9M, which isn't really that bad. .lua modules can install into their usual path below $WORLDTMP/legacy and we'll pick them up automagically by way of the ctor that sets up LUA_PATH early on. This re-lands bootstrap module support with a more sensible subset, and after having verified that it cross-builds fine on macOS and Linux -- we cannot do libfreebsd on !FreeBSD because it's more system header dependant. We also need to bootstrap libmd to bring in libhash, and libucl + libyaml. Reviewed by: bapt, emaste (both previous version) Differential Revision: https://reviews.freebsd.org/D51890 2025-10-04T00:53:28Z Kyle Evans kevans@FreeBSD.org 2025-10-04T00:52:36Z urn:sha1:bbef1c72b4873b657fdb0466b48b15d1d4f0a731 This reverts commit 1953a12ee2cde1afacb3e3f7612d89695c96e04f, because it cannot work at all on macOS without more work, at a minimum. We use linker sets for module discovery, but we don't have a version of this that works for mach-o at the moment. 2025-10-03T18:09:14Z Kyle Evans kevans@FreeBSD.org 2025-10-03T18:09:03Z urn:sha1:1953a12ee2cde1afacb3e3f7612d89695c96e04f This version builds every module into the flua binary itself, since all of the bootstrap tools are built -DNO_SHARED. As a result, we also cannot dlsym(), so we can't really discover the names of our newly builtin modules. Instead, just build out a linker set with all of our luaopen_*() functions to register everything up-front. Building in all of the modules isn't strictly necessary, but it means that we have an example of how to add a bootstrap module everywhere you go and one doesn't need to consider whether bootstrap flua can use a module when writing scripts. On my build machine, the consequence on our binary size is an increase from around 1.6M -> 1.9M, which isn't really that bad. .lua modules can install into their usual path below $WORLDTMP/legacy and we'll pick them up automagically by way of the ctor that sets up LUA_PATH early on. Reviewed by: bapt, emaste Differential Revision: https://reviews.freebsd.org/D51890 2025-10-01T09:28:56Z Dag-Erling Smørgrav des@FreeBSD.org 2025-10-01T09:28:30Z urn:sha1:b5e2bd5ef38181ce4a445ec19f1fa5cb6c8ea692 When an asterisk is encountered inside a C-style comment, we first check if there is at least one more character left in the buffer, and if that character is a slash, which would terminate the comment. If that is not the case, the next two characters are consumed without being inspected. If one of those is a double quote, or the initial asterisk of an asterisk-slash pair, we end up misparsing the comment. MFC after: 3 days Reviewed by: kevans, bofh Differential Revision: https://reviews.freebsd.org/D52808 2025-08-27T18:36:57Z Muhammad Moinur Rahman bofh@FreeBSD.org 2025-08-27T18:36:12Z urn:sha1:2326db40a1d2dd98631d70aae200ca52575139fb - Add FREEBSD-upgrade instructions - Add FREEBSD-Xlist file - Remove all unnecessary files which are not required for in-tree build Approved by: bapt Differential Revision: https://reviews.freebsd.org/D50472 Event: Oslo Hackathon 202508 Sponsored by: The FreeBSD Foundation 2025-08-04T19:38:06Z John Baldwin jhb@FreeBSD.org 2025-08-04T19:38:06Z urn:sha1:47586ffc8bde236bab65da05ad3c0a660709ba96 This is a wrapper around ucl_object_tostring_forced. Sponsored by: Chelsio Communications Pull Request: https://github.com/freebsd/freebsd-src/pull/1794 2024-02-29T12:27:03Z Baptiste Daroussin bapt@FreeBSD.org 2024-02-29T12:27:03Z urn:sha1:ddca081d382c7275bb6328c730182a007334c939 2021-03-22T15:42:18Z Cy Schubert cy@FreeBSD.org 2021-03-22T15:42:18Z urn:sha1:048488c0c4e47aa2aac9709b18d7da14b06f78cd