Bug 248778

Summary:	app-misc/twin fails to merge with sys-devel/bison-2.4-r1
Product:	Gentoo Linux	Reporter:	torindel
Component:	Current packages	Assignee:	SpanKY <vapier>
Status:	RESOLVED WONTFIX
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	249334
Attachments:	build log with bison-2.4-r1 build log with bison-2.3

Description torindel 2008-11-25 11:20:38 UTC

app-misc/twin fails to build with sys-devel/bison-2.4-r1 (2.3 works fine)

Reproducible: Always

Steps to Reproduce:
1. merge bison-2.4-r1
2. merge twin
3.

Comment 1 Rafał Mużyło 2008-11-25 16:00:59 UTC

Thank you for your non-report.
Could you, at the very least, attach your build.log ?

Comment 2 torindel 2008-11-25 19:15:55 UTC

Created attachment 173375 [details]
build log with bison-2.4-r1

Comment 3 torindel 2008-11-25 19:16:27 UTC

Created attachment 173377 [details]
build log with bison-2.3

Comment 4 torindel 2008-11-25 19:25:29 UTC

(In reply to comment #1)
> Thank you for your non-report.
> Could you, at the very least, attach your build.log ?
> 

You could just follow steps to reproduce to get your own copy of build.log, and being mean wont help you with that.

Comment 5 Rafał Mużyło 2008-11-26 00:47:08 UTC

Perhaps being mean is not helpful, but neither is posting bug reports with near zero content.

As a sidenote: gzip!=text/plain.

As for the bug, I think this part of the bison NEWS file may apply:

* Except for LALR(1) parsers in C with POSIX Yacc emulation enabled (with `-y',
  `--yacc', or `%yacc'), Bison no longer generates #define statements for
  associating token numbers with token names.  Removing the #define statements
  helps to sanitize the global namespace during preprocessing, but POSIX Yacc
  requires them.  Bison still generates an enum for token names in all cases.

Comment 6 Rafał Mużyło 2008-11-26 00:49:23 UTC

Also, if YOU want to get the bug fixed, it is YOU who should
give as much *relevant* info about the bug as possible.

Comment 7 Jeroen Roovers (RETIRED) gentoo-dev

2008-11-26 20:31:02 UTC

(In reply to comment #4)
> (In reply to comment #1)
> > Thank you for your non-report.
> > Could you, at the very least, attach your build.log ?
> > 
> 
> You could just follow steps to reproduce to get your own copy of build.log, 

And what if it failed to fail on my system? We'd just end up back at the point where you are to post your build log. :)

Comment 8 Samuli Suominen (RETIRED) gentoo-dev

2008-12-06 00:42:37 UTC

Removed from tree.