Date: Tue, 5 Dec 2017 14:06:54 -0700 From: Warner Losh <imp@bsdimp.com> To: Ryan Stone <rysto32@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Build failure in stand Message-ID: <CANCZdfpdkx0vzWHyWQRKfVC=kOJwpXEr7JdGD9rjE=cRHhoNAg@mail.gmail.com> In-Reply-To: <CAFMmRNxjjK%2ByfgKOWZcebm=Zpwr2%2BNX0T=Xp1WKE=acLXhwujQ@mail.gmail.com> References: <CAFMmRNwSKOB57uYwCrMotgh9cfp881maOhu57ASV9zg3hn0c-Q@mail.gmail.com> <CANCZdfoai5RCfnwCJ1vvNYPkQPTewmniEEnQuKR=FTcXEvwtBA@mail.gmail.com> <CANCZdfp1-2AU_cRrpyByJnbTYddptPN6kisviAecXZtNBQL5rA@mail.gmail.com> <CANCZdfokZND6Y1u0Wd3C-NeAXk4eayU6MTqwaWtKCzxBKHex6Q@mail.gmail.com> <CAFMmRNxjjK%2ByfgKOWZcebm=Zpwr2%2BNX0T=Xp1WKE=acLXhwujQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 5, 2017 at 2:03 PM, Ryan Stone <rysto32@gmail.com> wrote: > So I don't fully understand why this build failure happened, but I did > manage to find root cause. It turns out that there was a bug in make > that caused our build infrastructure to write objects and other build > output to the srcdir rather than the objdir in certain cases when > using make -C. I have a workaround in place for now and bdrewery@ is > working on a fix for the build infrastructure. > OK. That makes sense. It's caused by using the amd64 cpufuncs file being used when compiling on i386 (aka -m32). I have some fixes that should make it less likely to be an issue in the works... Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfpdkx0vzWHyWQRKfVC=kOJwpXEr7JdGD9rjE=cRHhoNAg>