Re-enable userspace rcu now that sh3/sparc/vax have been fixed.

remove userspace rcu from the build for now. Need to add
- non v9 sparc support
- sh3 support
- vax support

Add liburcu to the build and move libuv to the next trench since it is
not needed sooner.

move libzstd into the earlier depend group.

both libarchive and libfile depend upon libzstd, but they were all in the
same group and if you try hard enough, you can trigger a build failure in
one of

move libzstd into the earlier depend group.

both libarchive and libfile depend upon libzstd, but they were all in the
same group and if you try hard enough, you can trigger a build failure in
one of them if it hasn't finished building libzstd yet.

(surprised no one else hit this since october 30.)

show more ...

Hook zstd to the build and enable it for libarchive and file.

Handle multiple versions of jemalloc

Fix gdb's llvm build

GCC sanitizers: only build the sanitizers if $MKGCCCMDS != "no".

there's a minor use-case for the configuration of "building sanitizers
for distribution, but not the compiler", but it's pretty uncom

GCC sanitizers: only build the sanitizers if $MKGCCCMDS != "no".

there's a minor use-case for the configuration of "building sanitizers
for distribution, but not the compiler", but it's pretty uncommon, and
the latest sanitizers don't build at all on m68000 so enhance the
option to not build /usr/bin/gcc (which simply can't modern GCC on a
sun2) to not build the sanitizers either.

(if we were to split these, MKGCCSANITIZER would be good variable.)

update set lists for far too many files, including fixing MKDEBUG for
a couple of builds.

show more ...

revert previous - it doesn't mean what i thought and some builds broke.

skip sanitizers if MKSANITIZER "no".

lib: Handle various external lib directories with build_install.

This way, update builds track shlib major bumps correctly.

For example, suppose you had built Heimdal's libkrb5.so.27 and
libgssapi.

lib: Handle various external lib directories with build_install.

This way, update builds track shlib major bumps correctly.

For example, suppose you had built Heimdal's libkrb5.so.27 and
libgssapi.so.11 linked against it, and then you updated past the recent
shlib major bump raising them to libkrb5.so.28 and libgssapi.so.12.

Without this change, the build will make the following sequence of
targets (interleaved with some others):

1. make dependall in libkrb5
2. make dependall in libgssapi
3. make install in libkrb5
4. make install in libgssapi

The existing .WAIT tags in SUBDIR ensure that (1) happens before (2)
and (3) happens before (4). Unfortunately, this sequence is wrong,
because it will produce the following effect:

1. make dependall in libkrb5 builds libkrb5.so.28
2. make dependall in libgssapi builds libgssapi.so.12, linked against
libkrb5.so.27
3. make install in libkrb5 installs libkrb5.so.28
4. make install in libgssapi installs libgssapi.so.12

Why the out-of-date libkrb5.so.27 in step (2)? Because we just pass
-L${DESTDIR}/usr/lib -lkrb5 to the linker (or the equivalent with
--sysroot and implied -L/usr/lib), and ${DESTDIR}/usr/lib still has
only libkrb5.so.27 by the time of step (2), not libkrb5.so.28.

Now any applications that link against libkrb5.so _and_ libgssapi.so
will get libkrb5.so.28 and libgssapi.so.12 -- but transitively, via
libgssapi.so.12, they will also get libkrb5.so.27, which is a recipe
for disaster.

Splicing the Heimdal library subdirectories into lib/Makefile, as
this does, ensures that we run make dependall _and_ make install in
libkrb5 _before_ make dependall in libgssapi, giving the following
correct sequence:

1. make dependall in libkrb5 builds libkrb5.so.28
2. make install in libkrb5 installs libkrb5.so.28
3. make dependall in libgssapi builds libgssapi.so.12, linked against
libkrb5.so.28
4. make install in libgssapi installs libgssapi.so.12

Note that LIBDPLIBS isn't enough here, as implemented. LIBDPLIBS
ensures that the incremental build will remake libgssapi.so. But it
doesn't ensure that the new libkrb5.so.28 is available before then,
so it doesn't prevent this problem.

We use the same mechanism for crypto/external/bsd/openssl/lib
already; this just extends it to other external library collections.

As an alternative, in principle perhaps we could teach LIBDPLIBS to
ensure that libkrb5.so comes out of the libkrb5 objdir, and not out
of ${DESTDIR}/usr/lib. But that requires some work to make happen,
and make it reliable, whereas this approach we've already confirmed
works without other adverse consequences (besides leaving
grody-looking mechanism lying around) for the libcrypto major bump
already. We need to get this pulled up to the branch so all the
other major bumps it required are handled correctly by update builds.

XXX pullup-10

show more ...

lib/Makefile: Hook libgmp also for MKGDB=yes build

Now, gdb 13 can be built by clang, at least on amd64.

Include the OpenSSL Makefile fragment so that build_install works on each
OpenSSL subdirectory.

Introduce libc_aligned.so for evbppc-powerpc32, which provides
strictly-aligned versions of memcmp(3), bcopy(3), memcpy(3), and
memmove(3).

This is used for 403 by ld.so.conf with machdep.no_unalign

Introduce libc_aligned.so for evbppc-powerpc32, which provides
strictly-aligned versions of memcmp(3), bcopy(3), memcpy(3), and
memmove(3).

This is used for 403 by ld.so.conf with machdep.no_unaligned variable.

With this library, unaligned memory accesses are significantly reduced
for 403 (from several hundreds to few tens per sec under heavy load);
only ld.elf_so (typically few times per fork) and statically-linked
binaries do such access.

show more ...

cgdconfig(8): Add an argon2id password-based key generation method

This provides an extra level of side-channel and cracking resistance
compared to the pre-existing pkcs5_pbkdf2/sha1 method used for

cgdconfig(8): Add an argon2id password-based key generation method

This provides an extra level of side-channel and cracking resistance
compared to the pre-existing pkcs5_pbkdf2/sha1 method used for
password-based disk encryption.

Several new keygen parameters are supported:

memory (integer, in kilobytes)
parallelism (integer, usually the number of CPU cores)
version (integer, usually 19...)

We do our best to calibrate these automatically when the paramsfile
is initially generated.

lgtm riastradh@

show more ...

Use ${MACHINE_MIPS64}

Avoid duplicate directory traversals when building Elftoolchain sources.

Redo r1.288: traverse the complete imported Elftoolchain tree during a build.

Attempt to unbreak the build by reverting r1.288.

Traverse the complete imported Elftoolchain tree during a build.

Add blocklist support to libwrap which enables all programs using libwrap
to block access from hosts we deny. (libwrap support from Greg A. Woods)

lib: Move sqlite, since it depends on libm

Add HAVE_NVMM and use it to control the build of NVMM related components.
Defined to "yes" on amd64, "no" everywhere else.

Rename blacklist -> blocklist

Add libuv