--rBvYE4HrSVE32kP+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 30, 2004 at 10:28:37PM +0200, Ronald van der Pol wrote:
  | > =3D=3D=3D> build.sh command: build.sh -u -U -M /net/NetBSD/obj-i386 -=
T /net/NetBSD/tools-i386 -D /net/NetBSD/build-i386 -V MKTOOLS=3Dno -w /tmp/=
foo install=3D/
  |=20
  | [...]
  |=20
  | Did something change? The command above does not work anymore.
  | /mnt/foo is on a readonly NFS filesystem.
  |=20
  | # sh build.sh -o -u -U -M /mnt/foo/obj-i386 -T /mnt/foo/tools-i386 \
  | -D /mnt/foo/build-i386 -V MKTOOLS=3Dno -w /tmp/foo install=3D/
  | =3D=3D=3D> build.sh command: build.sh -o -u -U -M /mnt/foo/obj-i386 -T =
/mnt/foo/tools-i386 -D /mnt/foo/build-i386 -V MKTOOLS=3Dno -w /tmp/foo inst=
all=3D/
  | =3D=3D=3D> build.sh started: Fri Apr 30 22:24:10 CEST 2004
  | =3D=3D=3D> MACHINE:          i386
  | =3D=3D=3D> MACHINE_ARCH:     i386
  | =3D=3D=3D> TOOLDIR path:     /mnt/foo/tools-i386
  | =3D=3D=3D> DESTDIR path:     /mnt/foo/build-i386
  | =3D=3D=3D> RELEASEDIR path:  /mnt/foo/src/releasedir
  | =3D=3D=3D> makewrapper:      /tmp/foo
  | =3D=3D=3D> Updated /tmp/foo
  | installsets =3D=3D=3D> distrib/sets   (with: INSTALLDIR=3D/ INSTALLSETS=
=3D)
  | cd /mnt/foo/src/distrib/sets &&  DESTDIR=3D/mnt/foo/build-i386  MACHINE=
=3Di386 MACHINE_ARCH=3Di386  CKSUM=3D/mnt/foo/tools-i386/bin/nbcksum MAKE=
=3D/mnt/foo/tools-i386/bin/nbmake MTREE=3D/mnt/foo/tools-i386/bin/nbmtree  =
MKTEMP=3D/mnt/foo/tools-i386/bin/nbmktemp PAX=3D/mnt/foo/tools-i386/bin/nbp=
ax HOST_SH=3Dsh  sh ./maketars -d /mnt/foo/build-i386  -M /mnt/foo/build-i3=
86/METALOG -N /mnt/foo/src/etc   -i /=20
  | ./maketars: cannot create /mnt/foo/build-i386/etc/mtree/set.base: permi=
ssion denied


Yes, the "set manifest lists" are built on the fly each build,
and that's failing for you because your build tree is read-only.

I haven't yet investigated the changes required to support your
configuration; it may be that the cost/benefit ratio of fixing
this (versus the extra complexity) just isn't worth it (to me).

As always, you should be able to build the sets and extract
those on the target system.

--rBvYE4HrSVE32kP+
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQFAp0cIpBhtmn8zJHIRAltrAJ9dXHTfLsBd8/m68dBEmi1QB8fQ4QCcDXVK
MTT8bgjUnzx+TDKgiu250Ow=
=4W9y
-----END PGP SIGNATURE-----

--rBvYE4HrSVE32kP+--