Date: Sun, 23 Mar 2014 22:31:58 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Warner Losh <imp@bsdimp.com> Cc: toolchain@freebsd.org, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: [releng_10 tinderbox] failure on arm/arm Message-ID: <BDDEA1DC-2D74-4E2F-9D8E-1ACBB58DC73E@FreeBSD.org> In-Reply-To: <8EA3BF27-225E-4818-8983-8793FCDF08D9@bsdimp.com> References: <201403231522.s2NFM5Kc019213@worker01.tb.des.no> <8EA3BF27-225E-4818-8983-8793FCDF08D9@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On 23 Mar 2014, at 17:59, Warner Losh <imp@bsdimp.com> wrote: > About the time clang was MFC’d, this started appearing. It has been several days now. > > Did the clang MFC botch something? Was the timing just a coincidence? I hope the latter, but I didn't investigate yet. I do know that I ran a make universe before the clang 3.4 merge, and that worked just fine. That said, at first glance this looks like some sort of scripting problem? Does anybody know off the top of their heads where ARM_NARCH and ARM_NMMUS are coming from? -Dimitry [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iEYEARECAAYFAlMvUtEACgkQsF6jCi4glqNwdQCgx3joabmx/I3AvpyTnLen9RWg 3r8AnRfhvmBqK+RvihvHs2kq7CN4CoOj =KQec -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BDDEA1DC-2D74-4E2F-9D8E-1ACBB58DC73E>