Date: Thu, 11 Sep 2014 09:18:20 -0500 From: Tim Daneliuk <tundra@tundraware.com> To: freebsd-stable@freebsd.org Subject: Re: 10-STABLE Buildworld Failing Message-ID: <5411AF2C.6080002@tundraware.com> In-Reply-To: <201409110108.s8B18I6b002865@dyslexicfish.net> References: <54109820.1030905@tundraware.com> <CAKFCL4UHxuKqJZBSWEo=GLzL-vizTCutSgCU7XVLj=2yZQ7pPQ@mail.gmail.com> <54109CA5.7050807@tundraware.com> <CAKFCL4V5VFw=GFzx6FWMEYKbSe2okHoHF62N3L05yjAONuH43A@mail.gmail.com> <5410D4D7.8060906@tundraware.com> <201409110108.s8B18I6b002865@dyslexicfish.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 09/10/2014 08:08 PM, Jamie Landeg-Jones wrote: > Tim Daneliuk <tundra@tundraware.com> wrote: > >> Well something has definitely changed of late. Not only do I now have >> to cleanup the env variable with proper quoting, > > You say that as if it's a bad thing! Well, no, it's not a bad thing. What is a bad thing is unexplained sudden changes in system behavior. In this case the inability to use parallelized makes for buildworld and kernels (I used to use -j8, now no parallelization level works reliably) is more than tripling compliation time. ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5411AF2C.6080002>