Summary: | net-dialup/linux-atm-2.5.0 doesn't build with bison 2.4 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Grzegorz {NineX} Krzystek <ninex> |
Component: | [OLD] Unspecified | Assignee: | Gentoo Dialup Developers <net-dialup> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alexander.huemer, bugs, dliana, eddie692962, jarausch, non7top |
Priority: | Highest | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Grzegorz {NineX} Krzystek
2008-11-21 15:59:53 UTC
Which version of sys-devel/bison do you have installed? (In reply to comment #1) > Which version of sys-devel/bison do you have installed? > bison-2.4-r1 I'm having this problem as well. Everything's the latest and this has been bombing out lately. It worked fine a couple weeks ago, but I had to recompile the system (ooops..) and now this isn't compiling correctly. My system (well. router..) is a Dual P3@1GHz running a Reiser4-enabled gentoo-sources-2.6.27-r4 kernel. Apparently there is a bug in bison-2.4-r1. Following source lines are present in the .y file: %union { const char *str; int num; FIELD *field; VALUE *value; VALUE_LIST *list; TAG *tag; NAME_LIST *nlist; }; %token TOK_BREAK TOK_CASE TOK_DEF TOK_DEFAULT TOK_LENGTH TOK_MULTI %token TOK_RECOVER TOK_ABORT %token <str> TOK_ID TOK_INCLUDE TOK_STRING %type <field> rep_block block fields field field_cont %type <num> opt_break opt_pos decimal opt_more %type <value> opt_val value %type <tag> tags rep_tags %type <list> list %type <str> opt_id opt_recover %type <nlist> opt_name_list As you can see, both "rep_tags" and "tags" tokens have the type "tag", but for some reason bison fails to process it. same problem here. was the bug reported upstream? is there a temporal fix? emerge --info: # emerge --info Portage 2.2_rc23 (default/linux/amd64/2008.0, gcc-4.3.3, glibc-2.9_p20081201-r2, 2.6.28-gentoo-r1-blackbit x86_64) ================================================================= System uname: Linux-2.6.28-gentoo-r1-blackbit-x86_64-Intel-R-_Xeon-R-_CPU_E5420_@_2.50GHz-with-glibc2.2.5 Timestamp of tree: Tue, 17 Feb 2009 14:30:01 +0000 app-shells/bash: 3.2_p48-r1 dev-java/java-config: 1.3.7-r1, 2.1.7 dev-lang/python: 2.5.4-r2 dev-python/pycrypto: 2.0.1-r6 dev-util/cmake: 2.6.2-r1 sys-apps/baselayout: 2.0.0 sys-apps/openrc: 0.4.3-r1 sys-apps/sandbox: 1.3.7 sys-devel/autoconf: 2.13, 2.63 sys-devel/automake: 1.5, 1.8.5-r3, 1.9.6-r2, 1.10.2 sys-devel/binutils: 2.19.1 sys-devel/gcc-config: 1.4.1 sys-devel/libtool: 2.2.6a virtual/os-headers: 2.6.28-r1 ACCEPT_KEYWORDS="amd64 ~amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -pipe -march=nocona" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c /etc/udev/rules.d" CXXFLAGS="-O2 -pipe -march=nocona" DISTDIR="/usr/portage/distfiles" FEATURES="ccache distlocks fixpackages preserve-libs protect-owned sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LDFLAGS="" LINGUAS="en de" MAKEOPTS="-j5" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles -exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/portage/local/layman/mozilla /usr/portage/local/layman/sunrise /usr/portage/local/layman/dirtyepic /usr/portage/local/blackbit-overlay" SYNC="rsync://rsync.gentoo.org/gentoo-portage" I think, it's time for me to be my unhelpful self again. Comment 4 is completely off-topic. While my bison knowledge hasn't improved since then, I kindly point you to bug 246262 comment 7. This looks like exactly the same case - src/qgen/ql_y.y is broken and bison 2.4 simply noticed that. Only sane way to fix it is to patch that file. As upstream seems dead, distro has to provide it. Maybe some already do. thanks for the pointers. this makes clear that it is not the fault of bison and that later versions/revisions will not help. upstream of linux-atm is not completely dead. i am subscribed to the mailing list and get responses to my questions most of the time. i posted something about this issue today. it is indeed a good idea to take a look at the patch-sets of other distros, but in case a patch already exists it would be a shame that is wasn't posted on the ML. Reassigned to net-dialup team. Fixed in cvs, w/o rev bump. I find this bison error quite strange. IMHO $$ should be equivalent with LHS, regardless of the rule position. |