[libc++][CI] run-buildbot and libcxx-lit need a way to pass the paths to cmake and ninja (#213511)
macOS/Xcode don't have cmake or ninja anywhere in a default PATH, so
run-buildbot and libcxx-lit fail unless you do some PATH surgery before
running them. Allow passing them as environment variables instead, so
run-buildbot can be invoked as `CMAKE=$(xcrun --find cmake)
NINJA=$(xcrun --find ninja) CC=$(xcrun --find clang) CXX=$(xcrun --find
clang++) run-buildbot` on macOS. Allow cmake to be passed to libcxx-lit
in a similar fashion.
net-im/libsignal: fix build on powerpc64*
ring-sys 5.0.2] /wrkdirs/usr/ports/net-im/libsignal/work/target/release/build/boring-sys-ef33d39251a122cc/out/boringssl/crypto/fipsmodule/../internal.h:230:2: error: "Must define either OPENSSL_32_BIT or OPENSSL_64_BIT"
devel/perfetto: fix build on powerpc*
Currently build requires the target architecture to be
Android-supported. That doesn't make sense, since the tools
this port builds are to run on the target system, not Android.
devel/cbmc: fix build on powerpc64*
1. powerpc64 always uses 64-bit long double.
2. powerpc64le before 16.0 uses 64-bit long double and switched to
128-bit IEEE long double in 16.0.
devel/objfw: fix build on powerpc64*
Taking the address of _objc_taggedPointerClasses with
addis %r6, %r2, _objc_taggedPointerClasses at toc@ha
addi %r6, %r6, _objc_taggedPointerClasses at toc@l
emits an R_PPC64_TOC16_LO relocation against the symbol itself, which
requires the symbol to be non-preemptible and reachable relative to the
TOC pointer. Neither holds for a global symbol in a shared library, so
linking libobjfwrt.so fails on FreeBSD/powerpc64le:
ld: error: relocation R_PPC64_TOC16_LO cannot be used against symbol
'_objc_taggedPointerClasses'; recompile with -fPIC
>>> defined in tagged-pointer.lib.o
>>> referenced by lookup-asm.lib.o:(objc_msg_lookup) in archive
lookup-asm/lookup-asm.lib.a
The "recompile with -fPIC" hint is misleading: every object is already
[14 lines not shown]
science/siesta: don't set -march=native
On powerpc64le:
gfortran14: error: unrecognized command-line option '-march=native'; did you mean '-mcpu=native'?
libzfs: String trimming should not operate out of bounds
Forward slashes are trimmed from ZPOOL_IMPORT_PATH, but if someone sets
a ZPOOL_IMPORT_PATH that is only forward slashes, our trim code will
underflow the string, causing an out of bounds operation.
Similarly, the SMB code could potentially trim a string consisting of
only new line characters until it experiences the same bug. The same fix
is applied to it.
These are memory bugs, but I suspect that it is very unlikely that they
would cause a problem, since the probability that an out of bounds write
would follow the out of bounds read should be low. That said, going out
of bounds is undefined behavior, which could cause incorrect code
generation should a compiler look at it wrong, so let us fix this.
Reported-by: Grok 4.5 Build Beta
Signed-off-by: Richard Yao <richard at ryao.dev>
[3 lines not shown]
NAS-142044 / 26.0.0-BETA.3 / Protect persistent keyring (by anodos325) (#19466)
This commit adds a daily periodic task to refetch the persistent keyring
for uid 0. By default, persistent keyrings are garbage collected every 3
days with the timer reset on each fetch. Although there are typically
background tasks that fetch the keyring for uid 0, it's better to ensure
that it's always preserved since we store kerberos tickets, some session
information, and API keys in it.
Original PR: https://github.com/truenas/middleware/pull/19465
Co-authored-by: Andrew Walker <andrew.walker at truenas.com>
NAS-142044 / 26.0.0-RC.1 / Protect persistent keyring (by anodos325) (#19467)
This commit adds a daily periodic task to refetch the persistent keyring
for uid 0. By default, persistent keyrings are garbage collected every 3
days with the timer reset on each fetch. Although there are typically
background tasks that fetch the keyring for uid 0, it's better to ensure
that it's always preserved since we store kerberos tickets, some session
information, and API keys in it.
Original PR: https://github.com/truenas/middleware/pull/19465
Co-authored-by: Andrew Walker <andrew.walker at truenas.com>
[offload][test] Instruct clang-format to not reflow comments (#213696)
Without this, clang-format attempts to reflow check lines in tests,
resulting in broken tests.
net-p2p/amule: fix build on 32-bit platforms properly
The port asks for libatomic on 32 bit platforms. That's a gcc thing.
We don't compile with gcc, so libatomic is not needed in any case.
Patch out the check for libatomic to fix the build on all 32-bit
platforms.
Approved by: portmgr (build fix blanket)
MFH: 2026Q3
(cherry picked from commit b700cbd3a83de54d284f95fb5f6db0b241c0b1da)
sysutils/czkawka: fix build on armv7
Not enough address space for LTO on armv7.
Approved by: portmgr (build fix blanket)
MFH: 2026Q3
(cherry picked from commit a57f15aa583798a3682e53258e0141baf6a63d8e)
irc/halloy: fix build on armv7
The usual issue of time_t being 64 bits on armv7 despite it being a
32 bit platform. Refactor the time conversion code to just use i64
throughout, avoiding any type conversion issues.
Approved by: portmgr (build fix blanket)
See also: 0c9905d54dedcf8763df802a01beb2ea3d4ac4a0
MFH: 2026Q3
(cherry picked from commit 0075dbc93fe05ae068fbabaed8d356622b391f56)
