Just to mention, I haven't ran build.sh manually for years. I always install sysutils/sysbuild and sysupdate and have never had such a problem. Although my last rPi build was for 8.99.3,, so things may have changed.
Chavdar
On Sun, Nov 26, 2017 at 6:20 PM Robert Elz <kre%munnari.oz.au@localhost> wrote:Date: Sun, 26 Nov 2017 14:25:35 -0800
From: bch <brad.harder%gmail.com@localhost>
Message-ID: <CABfrOT8F-uvae_SRHDGrZ5mNZmND0vcCXNJ_zaOA9GocgtkdEw%mail.gmail.com@localhost>
| That's not fixing things... that's adjusting what used to be
| destdir.evbarm in the OBJDIR.
OK, just trying the simple things first...
Same here :)I was hoping somebody would be able to eyeball it and say “oh, you’re doing this incorrectly....” For my Pi, I got it’s image from nyftp.netbsd.org, but it’d be nice to be able to create arbitrary images on demand.Anyway, in the meantime I’ll look harder at it and see if it’s debuggable. Thanks for the hints :)-bch
It looks to be coming from src/distrib/utils/embedded/mkimage and in
particular from populate() in .../conf/armv7.conf
But it appears as if it should be going to /tmp/<something>/mnt/boot rather
than /boot.
Any chance that there is a mktemp (command) in your path which does not
work correctly?
As in where:
tmp="$(mktemp -d "/tmp/$PROG.XXXXXX")"
mnt="${tmp}/mnt"
leaves mnt as "" ?? (It seems a little unlikeloy!)
Apart from that possibility I don't see how this could happen in a current
install. Nothing else appears to alter ${mnt} and taht appears to be
where the files are placed. Or should be. That line should probably be
${TMPDIR:-/tmp) rather that just /tmp but that can't be the issue.
kre