Date: Wed, 22 Apr 2015 23:57:53 +0200 From: Willem Jan Withagen <wjw@digiware.nl> To: Ed Maste <emaste@freebsd.org> Cc: Warren Block <wblock@wonkity.com>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Newer yacc needed for building world Message-ID: <55381961.2040104@digiware.nl> In-Reply-To: <CAPyFy2CmUO65D6D6U4ywaRb4AadH=pqG-sziXEsQd0OKuSBXPg@mail.gmail.com> References: <5537C3BA.8010206@digiware.nl> <alpine.BSF.2.20.1504221045000.98242@wonkity.com> <5537FCA1.6010108@digiware.nl> <CAPyFy2CmUO65D6D6U4ywaRb4AadH=pqG-sziXEsQd0OKuSBXPg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 22-4-2015 23:37, Ed Maste wrote: > On 22 April 2015 at 15:55, Willem Jan Withagen <wjw@digiware.nl> wrote: >> >>> Yes: >>> https://lists.freebsd.org/pipermail/freebsd-current/2015-February/054740.html >>> >> >> But this is not enough to make yacc part of the build tools?? > > yacc is unconditionally built during bootstrap-tools as of r281615. > What SVN rev is your tree? > Can't get to the system atm, but freshly fetched this afternoon (GMT). Doing the recover trick as described above did the work. So it is hard to retest, other than to throw away /usr/bin/yacc and what comes of it. Given the fact that I found that I had more issues after my freebsd-upgrade of that system, it could be very well that this was a problem as a result of the same. Even though it was a fresh checkout. I'll do the yacc rename trick, and see if it still barks at me. If so I'll get back here. regards, --WjW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55381961.2040104>