./build.sh install-image: Should that work for all ports?

--V1NlN/V7gk8OJNgm
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi!

As a CI project, I'm doing quite a lot of automated NetBSD builds,
basically calling build.sh for
tools/libs/release and {iso,install,live}-image .  That's done on a
quite recent NetBSD -current VM (auto-installed from the install ISO
=66rom the previous round) as well as in a Linux-based Docker container
running `sid` Debian userland.

  I noticed that some in machine/architecture combinations (e.g.
evbarm with earmv4eb) the install-image doesn't build as it tries to
fetch kern-GENERIC (which isn't built.)

  Haven't yet tried, but would I need to also supply `kernel=3D<foo>` in
that case? Or something else (`releasekernel=3D<foo>` or `kernels` or
something like that?)  Or should these ports/archs set a proper kernel
on their own?

  (On the larger scale, that is to test reproducibility, and finally
reach a state where a Linux-based cross-build consistently and
continuously monitored produces the very same release artifacts as
does a NetBSD native build. The last breakage in that field was
non-matching INSTALL.ps files where a Linux-based build produces A4
while NetBSD produces US Letter output.)

Thanks,
  Jan-Benedict

--=20

--V1NlN/V7gk8OJNgm
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQQlDTvPcScNjKREqWEdvV51g5nhuwUCZWj3ywAKCRAdvV51g5nh
u+RkAKCIJFbOmrTIT6W+sbACwnYyaRep3ACdEjClmmXFqSznvGCt3CG4mCBvFaE=
=KPfm
-----END PGP SIGNATURE-----

--V1NlN/V7gk8OJNgm--