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

On Thu, Mar 11, 2004 at 04:48:18PM -0500, William Allen Simpson wrote:
  | Each year, the large number of destabilising changes I've observed=20
  | around the beginning of the year causes me to wait for the code to=20
  | settle.  This year was no different, so I've not compiled and installed=
=20
  | a new -current since Dec 24th.  With the recent call for testers, I've=
=20
  | tried for the past couple of days.  No joy!
  |=20
  | The sticking point today was an attempt to write into src/etc.  It=20
  | appears there are more problems with read-only src (in my case, merely=
=20
  | cvs'ing with a different user than building).
  |=20
  | It seems to me that build.sh should *never* write into the src tree.
  |=20
  | Using the command (completely fresh, cleaned-out obj):
  |   ./build.sh -O /usr/obj -T ../tools -u -U distribution

Does this occur if you change the objdir to something other than
/usr/obj?
What about if you use '-M /some/other/dir'?

I successfully build as non-root from a read-only src mountpoint
to an objtree that's not /usr/obj (e.g, "/var/obj/i386") all the time.

I suspect that there may be a problem with '-O /usr/obj' with certain
other conditions, but I haven't determined exactly what these are yet
because I don't hit the problem myself :/

--hYooF8G/hrfVAmum
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFAUOvdpBhtmn8zJHIRAujVAJ4+o/aOO1+M4DuMLGmYClb7ijokCgCfTKYG
6XtGPCae2Ix7aWhRsZNVXbY=
=pWK5
-----END PGP SIGNATURE-----

--hYooF8G/hrfVAmum--