#35327: graphviz: nawk: illegal jump type 339 ---------------------------+-------------------------- Reporter: runner0502@… | Owner: ryandesign@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: fixed | Keywords: Port: graphviz | ---------------------------+-------------------------- Comment (by ryandesign@…): Replying to [comment:6 egall@…]:
Either install gawk, or uninstall or deactivate nawk.
This seems to imply that if gawk is installed, that nawk does'''n't''' need to be uninstalled.
That's right. The configure script checks for awks in this order: gawk mawk nawk awk. This is nothing specific to Graphviz; this is part of the standard autoconf boildeplate in all configure scripts.
If this is the case, couldn't the build conflict be changed so that graphviz only has a build_conflict with nawk if gawk is not installed? Something like: {{{ if {[catch "registry_active gawk"]} { conflicts_build nawk } }}}
Possibly. But I don't know if this order of awk checks has changed in the past or is likely to change in the future. So I basically don't care about this. We've had to insert build conflicts with nawk into other ports for the same reason, so it doesn't appear to be a very good awk implementation, so I have no problem with pushing users toward realizing that and getting them to uninstall or at least deactivate it.
(also on an unrelated note, the notation for `if {![catch "registry_active ${badport}"]}` in the conflicts_build portgroup is kind of counterintuitive; I would have expected the usage of the `!` to be the other way around.)
It didn't think about it too much; I just put something that worked. -- Ticket URL: <https://trac.macports.org/ticket/35327#comment:7> MacPorts <http://www.macports.org/> Ports system for Mac OS