Date: Mon, 9 Nov 2015 10:05:09 -0800 From: Garrett Cooper <yaneurabeya@gmail.com> To: Ian Lepore <ian@freebsd.org> Cc: Chris H <bsd-lists@bsdforge.com>, freebsd-current@freebsd.org Subject: Re: buildworld broken Message-ID: <F4DAF1A2-82E7-4E24-9330-8B5409C93479@gmail.com> In-Reply-To: <1447091772.91534.483.camel@freebsd.org> References: <20151101164707.GA5847@troutmask.apl.washington.edu> <CD2B8B15-BFD7-48AA-BFAA-41BFE48635D7@gmail.com> <20151108182817.GA49944@troutmask.apl.washington.edu> <e066bd38f8b8bb46c5022ad6fbce3c3e@ultimatedns.net> <1447091772.91534.483.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Nov 9, 2015, at 09:56, Ian Lepore <ian@freebsd.org> wrote: ... >> I must perform a >> chflags -R noschg >> on /usr/obj prior to blowing it away. Is it different for you, >> or did you just omit that step? >=20 > In 19 years of using freebsd, I have never once needed to chflags on an > obj directory. Nothing in the build process sets any non-standard > flags in the obj dirs, and a simple rm -rf will remove everything just > fine (you would need to sudo the rm -rf if you built as root). I used to have to do that in earlier/custom versions of 10.x. Vanilla FreeBSD shouldn't be setting schg on files in MAKEOBJDIRPREFIX thoug= h, ever. Thanks, -NGie=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F4DAF1A2-82E7-4E24-9330-8B5409C93479>