>Number:         16343
>Category:       pkg
>Synopsis:       print/lilypond fails to build with older bison (1.28)
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Apr 13 15:54:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Jim Bernard
>Release:        NetBSD 1.5ZC
>Organization:
>Environment:
System: NetBSD zoo 1.5ZB NetBSD 1.5ZB (ZOO-$Revision: 1.70 $) #0: Sun Mar 10 14:35:50 MST 2002 jim@roc:/wd1/var/tmp/compile/sys/arch/i386/compile/ZOO i386
Architecture: i386
Machine: i386
>Description:
	The print/lilypond package uses bison as part of the build process,
	and if the installed bison is 1.28 (the current version in pkgsrc
	is 1.35), the build fails.  I don't have the failure message now, but
	I think I can supply a good approximation.  The successful build
	with bison-1.35 produced the following messages:

	  bison -d parser.yy
	  parser.yy:1385: warning: previous rule lacks an ending `;'
	  parser.yy contains 4 shift/reduce conflicts.
	  mv parser.tab.hh out/parser.hh

	It was at this stage that the build with bison-1.28 failed,
	complaining of "no such file or directory".  As I recall, the
	name of the file it was trying to mv was "parser.hh", not
	"parser.tab.hh", and that must have been the file that didn't
	exist.

>How-To-Repeat:
	Try to build lilypond with bison-1.28 installed.

>Fix:
	BUILD_DEPENDS+= bison>=1.35:../../devel/bison, I guess.
>Release-Note:
>Audit-Trail:
>Unformatted: