error: yacc.h: No such file or directory
Rodney W. Grimes
freebsd-rwg at gndrsh.dnsmgr.net
Wed Jun 19 16:30:26 UTC 2019
> In message <fffbe5d47e3515c960429ab416bf2ba234f9671d.camel at freebsd.org>
> , Ian Le
> pore writes:
> > On Tue, 2019-06-18 at 07:01 -0700, Enji Cooper wrote:
> > > > On Jun 18, 2019, at 06:59, Enji Cooper <yaneurabeya at gmail.com>
> > > > wrote:
> > > >
> > > >
> > > > > On Jun 18, 2019, at 06:53, Ian Lepore <ian at freebsd.org> wrote:
> > > >
> > > > ...
> > > >
> > > > > Last Saturday, Bryan (cc'd) made a series of commits (r349061-69)
> > > > > that
> > > > > were all somehow related to dependency processing in the
> > > > > build. I
> > > > > don't know the details, just remember seeing some commits about
> > > > > that.
> > > >
> > > > I remember that as well. This might have changed the dependency
> > > > order subtly, introducing a race.
> > > >
> > > > The headers might not be built in all cases in time now.
> > > >
> > > > Thanks,
> > > > -Enji
> > > >
> > > > PS This is one of the reasons why I wasn???t quick to discount Peter
> > > > Jeremy???s reported build issue.
> > >
> > > Correction: I meant Julian Stacey.
> >
> > Julian Stacey has 3 problems:
> >
> > 1. Missing opt_cam.h
> > 2. Missing yacc.h
> > 3. A years-long inability to report a problem without hurling personal
> > insults at the project and everyone associated with it.
> >
> > Because of #3, I don't much care about 1 and 2.
>
> Bingo! My point exactly!
You can't understand the frustration of 25 years of
having system build breakage on a pretty regular basis
as a trigger point for anger?
--
Rod Grimes rgrimes at freebsd.org
More information about the freebsd-current
mailing list