On Fri, Jan 20, 2006 at 03:31:14PM -0800, Paul Eggert wrote: > Kris Kennaway <[EMAIL PROTECTED]> writes: > > > Unfortunately there is a lot of software that cannot be used as-is > > with the newer version. This seems to be because the newer versions > > of bison are not backwards-compatible, which is irritating to say the > > least. > > That's news to me. Has anyone filed a bug report about these > irritating backward-compatibility issues to <[email protected]>?
I don't know about that, but I reran the build of all of our ~160 ports that use bison-1.75, with bison-2.1 instead. > Possibly the backward-compatibility problems, whatever they were, have > already been fixed. In that case I'd still recommend that people not > use 1.75, as it has some real bugs. Almost all of the ports built, which is a big improvement over the last time this was tried - but there are still two failures: lang/pike70 (ftp://ftp.oav.net/pike/7.0/) security/bro (ftp://ftp.ee.lbl.gov/) Perhaps these are the fault of the software depending on old bison bugs, but until they're both fixed (either by a patch to the software or a fix to bison) we can't switch any of the ports over to bison-2.1, since these two bison versions try to install on top of one another, so users will end up with a random version of bison which may or may not work. Kris
pgpwSLYYySPYC.pgp
Description: PGP signature
