From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 12:44:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0391B16A4CE for ; Fri, 12 Mar 2004 12:44:25 -0800 (PST) Received: from mail.voidnet.com (unknown [67.153.153.52]) by mx1.FreeBSD.org (Postfix) with SMTP id D5C1543D1F for ; Fri, 12 Mar 2004 12:44:21 -0800 (PST) (envelope-from timothy@voidnet.com) Received: from localhost.localdomain (67.153.153.100) by MAILSERV1 (MailMax 4. 8. 4. 0) with ESMTP id 41291928 for freebsd-current@freebsd.org; Fri, 12 Mar 2004 13:42:09 -0700 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: binary MIME-Version: 1.0 From: Eric Timme To: freebsd-current@freebsd.org X-Mailer: Magickal Paths WebMail Message-Id: <20040312204421.D5C1543D1F@mx1.FreeBSD.org> Date: Fri, 12 Mar 2004 12:44:21 -0800 (PST) Subject: Re: 5-CURRENT build errors X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Mar 2004 20:44:25 -0000 In my case this is an attempt to go from a fresh 5.2.1 install to 5-current. Could you recommend a date to sync to as a stepping stone to 5-current? I found others with similar problems dating from early February, and a post recommended rebuilding yacc from the source tree, installing, then trying another buildworld. I'm attempting that as we speak, I'll know in about 6 hours if it worked. skip.ford@verizon.net wrote: > Eric Timme wrote: > > I've had this build error over the last two attempted cvsups. I'm having a > > heck of a time finding a buildable/installable moment in time of the > > -current branch post PF changes. > > > > -Wno-format-y2k -Wno-uninitialized -c nslexer.c > > at-y2k -Wno-uninitialized -c nslexer.c > > /dev/stdout: In function `_nsyylex': > > /dev/stdout:711: warning: label `find_rule' defined but not used > > /mnt/ad1s3/src/lib/libc/net/nslexer.l: At top level: > > /dev/stdout:1678: warning: `yy_flex_realloc' defined but not used > > *** Error code 1 > > I received the same error. It seems to be a toolchain issue. > In my case, I was trying to build current on a system that hadn't > had the toolchain updated since last September because I defined > NO_TOOLCHAIN. Anyone who hasn't kept their world current should > also hit it though. > > I worked around it by installing a world including toolchain from > mid-February then building with that. > > -- > Skip >