Date: Thu, 02 May 2013 12:15:24 +0200 From: Dimitry Andric <dimitry@andric.com> To: Steven Hartland <killing@multiplay.co.uk>, Alfred Perlstein <alfred@ixsystems.com> Cc: hackers@freebsd.org Subject: Re: potential future proofing fix for aicasm build. Message-ID: <51823CBC.2060803@andric.com> In-Reply-To: <9C51B77A3AC948B68BAAFB9FB86DE52F@multiplay.co.uk> References: <51814686.2060805@ixsystems.com> <E2096D39-2037-4741-8F5B-9887220D7ACA@andric.com> <E8C064535571436A82136F7750006649@multiplay.co.uk> <518235B9.6090104@andric.com> <9C51B77A3AC948B68BAAFB9FB86DE52F@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2013-05-02 11:54, Steven Hartland wrote: > From: "Dimitry Andric" <dimitry@andric.com> ... >> Well, a way to reproduce the problem would be nice. I tried running >> "make buildkernel" in a stable/9 tree on a 10.0 machine, and building >> aicasm went just fine. So it works for me... > > I think what I did was the following:- > 1. make buildkernel KERNCONF=MYCONF -j10 # failed due to aicasm And this is what I cannot reproduce. Works just fine, either with or without -j.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51823CBC.2060803>