Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#49738 closed defect (fixed)

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

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: tenomoto (Takeshi Enomoto)
Priority: Normal Milestone:
Component: ports Version: 2.3.99
Keywords: haspatch Cc:
Port: nco

Description

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.

Attachments (3)

main.log (26.4 KB) - added by ryandesign (Ryan Carsten Schmidt) 9 years ago.
nawk.patch (404 bytes) - added by ryandesign (Ryan Carsten Schmidt) 9 years ago.
Portfile-nco.diff (429 bytes) - added by ryandesign (Ryan Carsten Schmidt) 9 years ago.

Download all attachments as: .zip

Change History (6)

Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Attachment: main.log added

Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Attachment: nawk.patch added

Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Attachment: Portfile-nco.diff added

comment:1 Changed 9 years ago by tenomoto (Takeshi Enomoto)

Resolution: fixed
Status: newclosed

Sent a pull request to upstream. Thanks.

comment:2 Changed 9 years ago by 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.

comment:3 Changed 9 years ago by 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.

Note: See TracTickets for help on using tickets.