From owner-freebsd-ports@FreeBSD.ORG Mon Jan 23 07:09:25 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DC5016A41F for ; Mon, 23 Jan 2006 07:09:25 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2767C43D53 for ; Mon, 23 Jan 2006 07:09:25 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id CB0C3407C; Mon, 23 Jan 2006 01:09:24 -0600 (CST) Date: Mon, 23 Jan 2006 01:09:24 -0600 To: Paul Eggert Message-ID: <20060123070924.GC27389@soaustin.net> References: <200601131825.SAA21164@sopwith.solgatos.com> <87r772obn8.fsf@penguin.cs.ucla.edu> <20060120211940.GA43031@xor.obsecurity.org> <87u0bymq7x.fsf@penguin.cs.ucla.edu> <20060122044224.GA81690@xor.obsecurity.org> <87lkx7zcsp.fsf@penguin.cs.ucla.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87lkx7zcsp.fsf@penguin.cs.ucla.edu> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: freebsd@sopwith.solgatos.com, bug-bison@gnu.org, freebsd-ports@freebsd.org, Kris Kennaway Subject: Re: portability fix for bison-1.75 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2006 07:09:25 -0000 On Sun, Jan 22, 2006 at 10:19:34PM -0800, Paul Eggert wrote: > Yes, in both cases. I'll follow up separately for each one. > Briefly, Pike is doing a "#define short int", which violates > section 7.1.3 of the C Standard, and bro is doing a > "#define YYLLOC_DEFAULT(Current, Rhs, N) Current = Rhs[N];", > which doesn't properly parenthesize the right-hand side of the macro. > > I'll check whether the bugs are still in the latest versions of these > programs, and if so I'll send a bug report to the upstream developers. > > However.... > > As far as I can tell, neither Pike 7.0 nor bro 0.8 is currently being > maintained by the upstream developer, so what procedure would you > prefer here, to make Bison 2.1 acceptable to you? Should I send you a > patch for these programs personally? Just send-pr and we'll try to catch them as they come in. mcl