When building a cross-compiled aarch64 toolchain, the CPPFLAGS are not
loaded properly at this step. The string "SPPFLAGS" only appears here
once in the gcc source; it is certainly just a typo for "CPPFLAGS".

Change-Id: I7eb23f6c2383016bf0c82ae6e990c3e3d1e4a9ce

Building netbsd-INSTALL_XEN3_DOMU fails with the following error:

    x86_64--netbsd-mdsetimage: fs image
    /tmp/guix-build-netbsd-stage-intermediate.drv-0/source/obj/distrib/amd64/ramdisks/ramdisk/ramdisk.fs
    (5120000 bytes) too big for buffer (48 bytes)

Skip this step, as we do not need a XEN kernel.

Change-Id: I6fc1ec00456c70caf11fa548665366736e21d814

Change-Id: I3858746f11d979ced5aee82da24d6e49b8ccf047

Fills in some gaps in HOST_SH/CONFIG_SHELL support used for overriding the host
system's shell path when building NetBSD.

Change-Id: I5521f116493379495d66550fc26216b446a4b0f0

Introduces a new variable HOST_BINENV to override the location of
/usr/bin/env in the build.sh system.

Change-Id: Ia6d4991df683043247b9546e668b1c2e0bb448b2

Patch the build script and toolchain to allow passing through
HOST_CPPFLAGS and HOST_CXXFLAGS in places where it was incomplete.
These variables are necessary to support building NetBSD from novel
host systems such as GNU Guix or NixOS, where /usr/include, /lib, are
reorganized.

Change-Id: Ia9cb7b94eba7e89ad9b99c4ebaf434ea94dfbf00

List the NO variables in order, leaving enough room to add more entries,
not splitting the next letter after "NO" across a line.

No functional change; just prettier and easier to review.

XXX
Pull up to netbsd-10 and netbsd-9.

This does real harm iff all of the following conditions are satisfied:

(1) On ILP32 architectures.
(2) Both LIBSA_PRINTF_LONGLONG_SUPPORT and LIBSA_PRINTF_WIDTH_SUPPORT
    compile-time options are enabled.
(3) Width field is used with 'l' modifier.

This is an implicit-fallthrough bug, but unfortunately, GCC 10.4 cannot
find this out somehow...

XXX
Pull up to netbsd-10 and netbsd-9. netbsd-8 is not affected.

Add more error handling to pax -r -w so that any failure
during the copy to the temporary file (including a failed flush)
prevents any existing destination file from being replaced
with the partial (including possibly empty) temporary file.
The partial temporary file is removed.  pax still exists non-zero.

Thanks to Michael van Elst (mlelstv@) for the analysis
of the problem in the PR.

Should fix PR misc/33753.

If copying a list of files from stdin, exit zero instead of non-zero
if there are no files supplied.

AFAICT, POSIX doesn't require a non-zero an error in this situation,
since there are no files to not match.

Fix from PR bin/41736 by Lloyd Parkes.

dtb + dtbsize

MKCRYPTO was removed by riastradh@ on 2017-05-22,
so remove references to it in comments.

MKCRYPTO was removed by riastradh@ on 2017-05-22,
so the NOCRYPTO override is now unnecessary.

Remove the leftover remnants of deprecated USE_COMBINE and NOCOMBINE,
as gcc -combine has been EOL for many years.

Completes the work done by maya@ on 2019-05-10 in bsd.kmodule.mk rev 1.61.

and mount the device path.  Cannot use "/rump/DEV" here as the device
path is embedded in "struct ufs_args" where it doesnt get hijacked.

more fine grained pacing of audio data. But this broke bta2dpd which
relied on full buffers returned (like reading from a file).

Replace the single read() in bta2dpd with a loop that fetches a full
buffer. This restores the old behaviour but loops in userland instead
of the kernel at the cost of a few extra system calls.

Also note that it's the same as PATH_MAX. Reflow the comment.

Suggested by Thierry Laronde.

The script has permissions 755 in the repo but ends up with permissions
644 in the source sets, therefore we cannot invoke it simply as
path/to/gen .

this commit doesn't reapply "dumping of the unicast server list
to the DumpStateLog debugging output" enhancement.
It doesn't build anymore, no idea how to rewrite.
Should fix PR 57442. Needs pull-ups for netbsd-9, netbsd-10.

This change broke the intention of recent changes to pad(4).

The solution to address PR/57436 must be done in bta2dpd(8).

Not likely to work in NetBSD base!

This restores the devcrypto engine, which was converted from static
to dynamic since the previous OpenSSL update.

XXX Pretty sure I got some of the set list package names wrong, but
it's not clear what the right ones are or what consequences any of
this has.

XXX Needs testing.

Turns out there is a regression lurking here: the devcrypto engine
was made dynamic-only (https://github.com/openssl/openssl/pull/7859),
so to maintain that functionality, we need to build dynamic engines.
Will fix the aarch64 build issue and wire things up separately.

around the code block with last_gd usage after the inner loop.
It may mainly happen on bus_dmamap_load error.
Reported by Mootja _14, 2017.

They fail with 'L1_S_SIZE' undeclared error otherwise from gemini.h declarations.
gemini_machdep.c includes it transitively, thus doesn't faili on GEMINI config.
Likely nobody is using them anyway though...

- Engines are deprecated in openssl 3.

- We never actually had the .so engines wired up to be built in
  openssl 1.1, and judging by the lack of obsolete entries in the set
  lists, I don't think we ever had them wired up to be built at all.

The previous commit was misleading due to the flag names used.

The rationale for this change is that it is ok to return EAGAIN on first
read as playback has not started.  Then it shoud wait on every subsequent read.

This is what makes the high precsision throttling of pad(4), for which these
degree of fine-grained sleeps are not possible in userland.  This is a
requirement of users of pad(4) such as bta2dpd(8).

- check cmd: run `sshd -t' to check sshd_config file

- reload precmd: run check cmd before reloading so we don't nuke sshd
  if there's an error in the sshd_config file

(It is still possible to effectively nuke sshd by changing the
configuration tosomething that won't work on your network, but at
least we avoid making sshd just exit on reload when you make a typo
in a config option.)

XXX pullup-9
XXX pullup-10