Luke Mewburn wrote :
| The build.sh semantics have changed.  This commit message should explain
| it all.  If not, UPDATING will.  If not, ask on current-users.

Looks like `./build.sh install=/` from a native NetBSD system doesn't
work with MACHINE unset: build.sh complains about "/" being impossible
for crossbuilds.
I had to use the -m  option to set MACHINE manually.

After a quick look at the script, it appears that in the case where
MACHINE is undefined its value is computed after the sanity checks for
the `install' option?