Date: Wed, 13 Aug 2025 15:19:24 +0300 From: Sulev-Madis Silber <freebsd-current-freebsd-org111@ketas.si.pri.ee> To: freebsd-current@freebsd.org Subject: =?US-ASCII?Q?Re=3A_buildworld_seems_to_fail_with_d83?= =?US-ASCII?Q?1bd8878db38c5c84477a2efa24bdbbf2fead6?= Message-ID: <1568CC55-2F9C-4C2F-BDD5-1C168D6AD669@ketas.si.pri.ee> In-Reply-To: <90966e9e-aa60-4052-99bd-78e24b70a89c@blastwave.org> References: <4bcaa009-102b-4e04-801e-9a258acc06bd@blastwave.org> <aJxzbqFDtI5yORKs@albert.catwhisker.org> <90966e9e-aa60-4052-99bd-78e24b70a89c@blastwave.org>
index | next in thread | previous in thread | raw e-mail
you could indeed nuke /usr/src or, you could use git status and / or git status --ignored to check tree changes, if you have them then git clean -nfdx to verify what to remove and git clean -fdx to finally remove offending changes but that culprit surely isn't in some options or in existing /usr/obj or in any (c)caches you might use? "nuclear option" on src tree gets quite a hassle after multiple tries but indeed does clean up everything really well while there, one can also copy and / or zfs snapshot a src tree, if git is a hassle to me git is first vcs ever that i really used as one, apart from a little svn. which i found easy to use but people varyhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1568CC55-2F9C-4C2F-BDD5-1C168D6AD669>