alas, the workaround you give in your mail doesn't do the trick for pike 7.2...:

language.yacc:1604.3-1608.9: $4 of `block' has no declared type language.yacc:2483.3-2484.20: $5 of `cond' has no declared type language.yacc:2483.3-2484.34: $7 of `cond' has no declared type

that's what appears when I add the empty nonterminal inbetween the actions of the offending rules. Unfortunately, for now I _have_ to come up with some workaround until the Debian bison maintainer uploads the fixed package - I could use some help on that one, if you don't mind. TIA.

/ Marek Habersack (Grendel)

Previous text:

2002-10-18 13:12: Subject: Pike 7.2 (latest CVS) and GNU bison 1.50 - no go...

---

2002-10-13 Paul Eggert eggert@twinsun.com

   Fix problem reported by Henrik Grubbstroem in
   <http://mail.gnu.org/pipermail/bug-bison/2002-October/001670.html>:
   "nonterm: { $$ = 123; } { $$ = $1; };" was wrongly rejected,
   because the Bison parser reads the second action before reducing
   the first one.
   * src/scan-gram.l (rule_length): New static var.
   Use it to keep track of the rule length in the scanner, since
   we can't expect the parser to be in lock-step sync with the scanner.
   (handle_action_dollar, handle_action_at): Use this var.
   * tests/actions.at (Exotic Dollars): Test for the problem.

/ Henrik Grubbström (Lysator)

it's not that easy. Pike build-depends on bison, so the autobuilder would pull whatever bison is in the distro - in this case 1.50 and I have no influence on that. But, as I said, 1.75 is on the way :-) - that'll take care of the problem. Thanks a lot.

/ Marek Habersack (Grendel)

Previous text:

2002-10-18 20:03: Subject: Pike 7.2 (latest CVS) and GNU bison 1.50 - no go...

---

Downgrade to a working bison?

/ Martin Nilsson (Fake Build Master)

I can have negative dependencies, look at the packaging/debian/control file. But if I build-conflicted on bison, then pike wouldn't get built - because there can be only one bison version installed on the system (actually, it is possible to have many versions - like autoconf which is in two flavors in Debian or automake which is in 3 flavors or pike in two flavors as well) but in this case it wouldn't make much sense since bison was undoubtedly buggy. Actually, the debian dependencies system is very powerful - if you have some time, read up about it on http://debian.org/devel/ in the Packaging section.

/ Marek Habersack (Grendel)

Previous text:

2002-10-18 20:10: Subject: Pike 7.2 (latest CVS) and GNU bison 1.50 - no go...

---

So you can't have a negative dependency on certain versions of software? If not it really sounds like a non-working package system. There is not much software that gets steadily better without new bugs and compatibility issues. Roxen, Pike, caudium, gcc, autoconf to name a few.

/ Martin Nilsson (Fake Build Master)

ok, scratch my last request ;) - I've just been notified that the maintainer is uploading bison 1.75 now :)

/ Marek Habersack (Grendel)

Previous text:

2002-10-18 13:12: Subject: Pike 7.2 (latest CVS) and GNU bison 1.50 - no go...

---

2002-10-13 Paul Eggert eggert@twinsun.com

   Fix problem reported by Henrik Grubbstroem in
   <http://mail.gnu.org/pipermail/bug-bison/2002-October/001670.html>:
   "nonterm: { $$ = 123; } { $$ = $1; };" was wrongly rejected,
   because the Bison parser reads the second action before reducing
   the first one.
   * src/scan-gram.l (rule_length): New static var.
   Use it to keep track of the rule length in the scanner, since
   we can't expect the parser to be in lock-step sync with the scanner.
   (handle_action_dollar, handle_action_at): Use this var.
   * tests/actions.at (Exotic Dollars): Test for the problem.

/ Henrik Grubbström (Lysator)