Page MenuHomeFreeBSD

flua: Always build as a bootstrap tool
ClosedPublic

Authored by ivy on Apr 6 2026, 1:45 PM.
Tags
None
Referenced Files
F167174239: D56270.id175022.diff
Wed, Aug 19, 4:10 PM
Unknown Object (File)
Mon, Aug 17, 10:30 PM
Unknown Object (File)
Sun, Aug 16, 10:31 AM
Unknown Object (File)
Fri, Aug 14, 3:46 AM
Unknown Object (File)
Thu, Aug 13, 12:48 AM
Unknown Object (File)
Wed, Aug 12, 12:52 AM
Unknown Object (File)
Tue, Aug 11, 8:26 PM
Unknown Object (File)
Mon, Aug 10, 6:53 AM
Subscribers
None

Details

Summary

We want to use flua from the source tree (not the host) during package
build, firstly to protect us from breaking changes in lua or libucl,
and secondly to allow (in future) cross-building of packages from
Linux or macOS.

Since we don't know if the user will be building packages during the
bootstrap phase, and because flua is fairly small and generally useful,
build it as a bootstrap tool unconditionally.

MFC after: 2 weeks
Sponsored by: https://www.patreon.com/bsdivy

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

ivy requested review of this revision.Apr 6 2026, 1:45 PM
ivy created this revision.

I'd /maybe/ consider leaving libmd behind a BOOTSTRAPPING == 0 since it's entirely a FreeBSD project, but I don't feel strongly about it -- libmd doesn't take that long to build.

This revision is now accepted and ready to land.Apr 6 2026, 1:49 PM

I'd /maybe/ consider leaving libmd behind a BOOTSTRAPPING == 0 since it's entirely a FreeBSD project, but I don't feel strongly about it -- libmd doesn't take that long to build.

Oh wait, the flua bootstrap build probably can't be split like that today- sorry.

This revision was automatically updated to reflect the committed changes.