From owner-freebsd-bugs@FreeBSD.ORG Sat Feb 6 04:05:24 2010 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E7D51065676; Sat, 6 Feb 2010 04:05:24 +0000 (UTC) (envelope-from austinenglish@gmail.com) Received: from mail-ww0-f54.google.com (mail-ww0-f54.google.com [74.125.82.54]) by mx1.freebsd.org (Postfix) with ESMTP id 945728FC16; Sat, 6 Feb 2010 04:05:23 +0000 (UTC) Received: by wwj40 with SMTP id 40so778308wwj.13 for ; Fri, 05 Feb 2010 20:05:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=RdOE2jGo8kenmlxpGv1GeyZ159ZH7zwNa8aKZi3Dw/M=; b=PPnqYfiNeMIFcF33OWBvAJRo9+kWO1LYMbk3xL8hOaTE/3n4HXq5y93KEBsrWAvNbv ntL8i8IhwWqcweQQMyw45n6tgGdhJGtLXMzFq544hUkTjCUjnR7NdNeTXiPSlZkrFnPr UecfwbdAe3SMhgMyl6J3pGNYGgYxvTG0Aoneo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=L0w2U2Q92lD137R3m7BxFf6cKBlHWYApghlLcQ8PT2v7jKjZZm9mawdEumG604ibOp 6amYIfgBGWzogbvyW2uGX8cn+Z1ihY5/M7Q1TpIkB+k9QrbE0ZQUExpBtIIUDD80yMaY 3PjeX/nM9oWGWaU7sIoAL4/BLUhZUIPB6BhLk= MIME-Version: 1.0 Received: by 10.216.86.72 with SMTP id v50mr1975437wee.184.1265429122197; Fri, 05 Feb 2010 20:05:22 -0800 (PST) In-Reply-To: <7d6fde3d1002012157i74be831bi501d76ad6d73da2a@mail.gmail.com> References: <201001300048.o0U0mkwD096197@freefall.freebsd.org> <7d6fde3d1002012157i74be831bi501d76ad6d73da2a@mail.gmail.com> From: Austin English Date: Fri, 5 Feb 2010 22:05:02 -0600 Message-ID: To: Garrett Cooper Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-bugs@freebsd.org, linimon@freebsd.org Subject: Re: bin/143351: [request] update flex(1) to at least 2.5.33 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Feb 2010 04:05:24 -0000 On Mon, Feb 1, 2010 at 11:57 PM, Garrett Cooper wrote: > On Mon, Feb 1, 2010 at 2:33 AM, Austin English = wrote: >> On Fri, Jan 29, 2010 at 6:48 PM, =C2=A0 wrote: >>> Old Synopsis: update flex to at least 2.5.33 >>> New Synopsis: [request] update flex(1) to at least 2.5.33 >>> >>> State-Changed-From-To: open->suspended >>> State-Changed-By: linimon >>> State-Changed-When: Sat Jan 30 00:45:41 UTC 2010 >>> State-Changed-Why: >>> Mark suspended awaiting someone to take up the (hard) task of deciding >>> if this will create regressions. =C2=A0See: >>> >>> http://lists.freebsd.org/pipermail/freebsd-current/2009-January/002233.= html >>> >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=3D143351 >> >> Indeed, it does. I did a build world to make sure it worked (using the >> freebsd9 snapshot), then installed flex 2.5.35 and rebuilt. >> /usr/src/cddl failed to build, and possible others (ran make -k, but >> haven't checked the log yet). Should I file bugs for each program that >> doesn't build in newer flex? or sit back and wait for someone to fix >> flex for BSD and then include it? > > =C2=A0 =C2=A0File bugs for any and all issues you find, point them back t= o this > PR, and as long as everything points in the right direction and is > done in proper order, everything should work just fine (TM). > =C2=A0 =C2=A0The version bump definitely deserves a heads up though in th= e > current@ and stable@ community though so people can fix prepare to fix > their potentially buggy / backwards incompatible yacc code, or bite > the bullet and multislot version their tools [via ports]. Actually, I was mistaken. I used flex from http://flex.sourceforge.net/, rather than the flex in ports. I just did a make clean ; make world with flex from ports, and everything builds fine (this is with FreeBSD-9.0-CURRENT-201001-i386). I also compared make's output, no new compiler warnings appear. Of course, this isn't a complete analysis, but things look much better than it initially appeared. --=20 -Austin