Date: Thu, 4 Jul 2013 13:32:29 -0700 From: Rui Paulo <rpaulo@FreeBSD.org> To: Jordan K. Hubbard <jordan.hubbard@gmail.com> Cc: FreeBSD ARM List <freebsd-arm@freebsd.org> Subject: Re: Most recent R-PI kernel refuses to build Message-ID: <F1C0AE20-B87A-41B7-BA15-0823C732BFBB@FreeBSD.org> In-Reply-To: <BADC50FE-815F-456F-9A56-6C3C08F5201D@turbofuzz.com> References: <20130704150959.76adeedf@ivory.wynn.com> <BADC50FE-815F-456F-9A56-6C3C08F5201D@turbofuzz.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4 Jul 2013, at 12:46, Jordan K. Hubbard <jordan.hubbard@gmail.com> = wrote: > On Jul 4, 2013, at 12:09 PM, Brett Wynkoop <freebsd-arm@wynn.com> = wrote: >=20 >> So is the only way for me to get caught up to head going to be do >> another cross build with Tim's tools. That seems nuts to me. >=20 > I think something is seriously spooged with your hosting environment. = You can't svn update. Your build metadata is corrupt (I'll bet a = dollar if you look in that kern.mk file, you'll find the tell-tale <<<< = markers of a merge conflict). If I were you I'd nuke that whole = system from orbit and start from scratch with a -current snapshot - it's = the only way to be sure! The problem was actually because we imported NetBSD's make and they are = incompatible now. Brett is trying to compile CURRENT with FreeBSD's make = which won't work. The fix is to use the method I described in my = previous email. -- Rui Paulo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F1C0AE20-B87A-41B7-BA15-0823C732BFBB>