From owner-freebsd-current@FreeBSD.ORG  Wed Apr 22 21:58:05 2015
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 4D9046AF;
 Wed, 22 Apr 2015 21:58:05 +0000 (UTC)
Received: from smtp.digiware.nl (unknown [IPv6:2001:4cb8:90:ffff::3])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 0D9901ADA;
 Wed, 22 Apr 2015 21:58:05 +0000 (UTC)
Received: from rack1.digiware.nl (unknown [127.0.0.1])
 by smtp.digiware.nl (Postfix) with ESMTP id F06AF16A57A;
 Wed, 22 Apr 2015 23:58:02 +0200 (CEST)
X-Virus-Scanned: amavisd-new at digiware.nl
Received: from smtp.digiware.nl ([127.0.0.1])
 by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id gicloq_3jX8V; Wed, 22 Apr 2015 23:58:01 +0200 (CEST)
Received: from [IPv6:2001:4cb8:3:1:254d:b807:25f8:f916] (unknown
 [IPv6:2001:4cb8:3:1:254d:b807:25f8:f916])
 by smtp.digiware.nl (Postfix) with ESMTP id 5EDB116A572;
 Wed, 22 Apr 2015 23:58:01 +0200 (CEST)
Message-ID: <55381961.2040104@digiware.nl>
Date: Wed, 22 Apr 2015 23:57:53 +0200
From: Willem Jan Withagen <wjw@digiware.nl>
Organization: Digiware Management b.v.
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64;
 rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
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
References: <5537C3BA.8010206@digiware.nl>
 <alpine.BSF.2.20.1504221045000.98242@wonkity.com>
 <5537FCA1.6010108@digiware.nl>
 <CAPyFy2CmUO65D6D6U4ywaRb4AadH=pqG-sziXEsQd0OKuSBXPg@mail.gmail.com>
In-Reply-To: <CAPyFy2CmUO65D6D6U4ywaRb4AadH=pqG-sziXEsQd0OKuSBXPg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2015 21:58:05 -0000

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