Date: Tue, 18 Jun 2019 11:02:33 -0600 From: Ian Lepore <ian@freebsd.org> To: Bryan Drewery <bdrewery@FreeBSD.org>, koobs@FreeBSD.org, Michael Tuexen <tuexen@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: error: yacc.h: No such file or directory Message-ID: <919c8e9795e842a8fff77941664a087a9c9aa152.camel@freebsd.org> In-Reply-To: <de47d99e-a38e-2b2f-8888-896e354adda9@FreeBSD.org> References: <0737312F-50AE-4526-B201-E62DB8949612@freebsd.org> <4b1f9f81-6463-c1bd-30a9-14aed49fc038@FreeBSD.org> <de47d99e-a38e-2b2f-8888-896e354adda9@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2019-06-18 at 09:51 -0700, Bryan Drewery wrote: > On 6/18/2019 3:56 AM, Kubilay Kocak wrote: > > Have seen another report on Twitter yesterday. Didn't see a full > > build > > log, but theirs was had apparently without -j, apparently on June > > 14 > > sources: > > > > Error: > > /usr/src/usr.bin/mkesdb/lex.1:46:10: fatal error: 'yacc.h' file not > > found > > > > Have not heard back from them whether it continued after trying -j2 > > but > > I did ask them to hit up freebsd-current if it continued to be an > > issue > > Even -j1 should avoid it. For some reason I am only seeing it without > any -j flag at all. > > I should have a fix in soon. > There's a subtle difference between -j1 and no -j at all, having to do with running in "compatibility mode". I forget the details, but I remember being burned by the difference once. :) -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?919c8e9795e842a8fff77941664a087a9c9aa152.camel>