Bug 47068

Summary: Update port: devel/bison to 1.875
Product: Ports & Packages Reporter: tkato <tkato>
Component: Individual Port(s)Assignee: Tilman Keskinoz <arved>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
file.diff none

Description tkato 2003-01-14 20:10:07 UTC 
- Update to version 1.875
Comment 1 Tilman Keskinoz freebsd_committer freebsd_triage 2003-01-24 11:49:11 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->arved

I'll handle this, after successfull test run
Comment 2 Tilman Linneweh 2003-02-11 23:20:04 UTC 
Just an Update on this PR. 
I am currently a bit too busy to investigate, Hopefully next weekend.
Stay tuned...

Begin forwarded message:

Date: Fri, 7 Feb 2003 20:51:57 -0800
From: Kris Kennaway <kris@obsecurity.org>
To: Tilman Linneweh <arved@FreeBSD.org>
Subject: Re: bison Upgrade


On Mon, Feb 03, 2003 at 12:32:32AM +0100, Tilman Linneweh wrote:

> > These all look like the same problem.
> 
> Okay lets see how many got broken, when the build finishes. 

Here's the final list broken by the new bison on i386 (all from the
"syntax error before `goto'"):

cflowd-2-1-b1_5
chemeq-1.10_1
cybervrml97-1.0.6
graphthing-0.7
htmltolatex-1
irrtoolset-4.7.2
ja-xjtext-1.3_1
mpqc-2.1.2
openh323-1.9.10_2
panorama-0.13.2_1
ptoc-3.50
ragel-1.4.1
xxdiff-2.0.3

It's possible that other ports may break on other architectures.

Kris
Comment 3 Tilman Keskinoz freebsd_committer freebsd_triage 2003-03-29 14:06:45 UTC 
State Changed
From-To: open->analyzed

The new alpha version of bison seems to fix these. But I am not trying to update 
our bison version to an alpha release.  

Lets wait until the next bison release
Comment 4 Tilman Keskinoz freebsd_committer freebsd_triage 2004-01-21 19:24:28 UTC 
State Changed
From-To: analyzed->closed

The new bison version has been added as a seperate port an d people seem to be happy with that, so i will close this PR so i will not get anymore annoying email.