nco @4.5.2: fix configure failure when nawk is installed but gawk and mawk aren't

[ryandesign (Ryan Carsten Schmidt)]

If nawk is installed but gawk and mawk aren't, nco fails to configure with this error:

config.status: creating config.h
nawk: illegal statement
 input record number 1, file config.h.in
 source line number 133
config.status: error: could not create config.h

Similar errors are common in other ports. I guess many ports' build systems use awk syntax that is not compatible with nawk.

We've been fixing this in other ports by patching the configure script so that it does not consider nawk as an awk candidate. See attached patch.

[tenomoto (Takeshi Enomoto)]

Sent a pull request to upstream. Thanks.

[ryandesign (Ryan Carsten Schmidt)]

Thanks. I doubt nco upstream will do anything, since checking for nawk is a feature of autoconf. If anyone, it would be the developers of autoconf who should be encouraged to change that. At least I've suggested we make that change in MacPorts: #49713. But that will only help ports that use autoreconf.

[ryandesign (Ryan Carsten Schmidt)]

Unless you meant you sent a pull request to nco upstream to make the nco configure script's usage of awk compatible with nawk. In which case they should accept that.