Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 23 Apr 2015 11:05:19 +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:  <5538B5CF.9010508@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/04/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?
> 

# svn info
Path: .
Working Copy Root Path: /usr/src
URL: svn://svn.freebsd.org/base/stable/10
Relative URL: ^/stable/10
Repository Root: svn://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 281853
Node Kind: directory
Schedule: normal
Last Changed Author: kib
Last Changed Rev: 281849
Last Changed Date: 2015-04-22 12:59:05 +0200 (Wed, 22 Apr 2015)

Then I removed /usr/obj/* to get a fresh start.
Removing yacc just gets me into trouble even earlier:

# make -j 32 buildworld
 .
 .
 .
--- _bootstrap-tools-usr.bin/compile_et ---
--- parse.c ---
yacc -d -o parse.c /usr/src/usr.bin/compile_et/../../contrib/com_err/parse.y
yacc: not found
--- _bootstrap-tools-usr.sbin/bsnmpd/gensnmptree ---
/usr/obj/usr/src/tmp/usr/src/usr.sbin/bsnmpd/gensnmptree created for
/usr/src/usr.sbin/bsnmpd/gensnmptree
--- _bootstrap-tools-usr.bin/compile_et ---
*** [parse.c] Error code 127

So I have relatively little further to test.
Perhaps the '-j 32' was a bit aggressive, but it gets fast where the
error is.

--WjW



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5538B5CF.9010508>