#41600: bison: update to 3.0.2 ------------------------------+---------------------- Reporter: akim.demaille@… | Owner: larryv@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: bison | ------------------------------+---------------------- Comment (by akim.demaille@…): Replying to [comment:25 larryv@…]:
Does omitting the `--disable-yacc` configure option change the build (other than installing the yacc executable, static library, and man page)? Is there a good reason we shouldn’t just do that always and get rid of the `yacc` variant?
{{{ if ENABLE_YACC bin_SCRIPTS = src/yacc endif EXTRA_SCRIPTS = src/yacc MOSTLYCLEANFILES += src/yacc }}} So if `--disable-yacc` is passed, yacc is not built by default (i.e., `make`) but `make src/yacc` would work. I personally don't understand the point of not installing `yacc`. Bison is designed to provide compatibility with yacc (when given `--yacc`), and that's precisely the point of `yacc`: to provide the user with a POSIX Yacc. We are talking about a shell-script of a couple of lines, why the bother? Byacc has always been called byacc, not yacc. -- Ticket URL: <https://trac.macports.org/ticket/41600#comment:29> MacPorts <https://www.macports.org/> Ports system for OS X