#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:8 egall@…]:
Really? Which other ports?
{{{ $ port file all | sort -u | xargs grep conflicts_build.*nawk /Users/rschmidt/macports/dports/graphics/graphviz- devel/Portfile:conflicts_build nawk /Users/rschmidt/macports/dports/graphics/graphviz-devel/Portfile: conflicts_build nawk /Users/rschmidt/macports/dports/graphics/graphviz/Portfile:conflicts_build nawk /Users/rschmidt/macports/dports/graphics/graphviz/Portfile: conflicts_build nawk /Users/rschmidt/macports/dports/lang/gawk/Portfile:conflicts_build nawk /Users/rschmidt/macports/dports/mail/libidn/Portfile:conflicts_build nawk /Users/rschmidt/macports/dports/net/wget/Portfile:conflicts_build nawk /Users/rschmidt/macports/dports/science/hdf5-18/Portfile:conflicts_build nawk }}} That's just the ones I know about. It wouldn't surprise me at all if other ports, possibly all ports using an autoconf-based configure script, fail when nawk is active and gawk is not. nawk doesn't seem very popular so I guess most users have not tried it, otherwise I think we'd have more bug reports about it. -- Ticket URL: <https://trac.macports.org/ticket/35327#comment:9> MacPorts <http://www.macports.org/> Ports system for Mac OS