Opened 9 years ago

Closed 7 years ago

Last modified 7 years ago

#49736 closed defect (worksforme)

c-ares @1.10.0: fix configure failure when nawk is installed but gawk and mawk aren't

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: tobypeterson
Priority: Normal Milestone:
Component: ports Version: 2.3.99
Keywords: haspatch Cc:
Port: c-ares

Description

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

:info:configure config.status: creating ares_config.h
:info:configure nawk: illegal statement
:info:configure  input record number 1, file ares_config.h.in
:info:configure  source line number 176
:info:configure config.status: error: could not create ares_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 (28.9 KB) - added by ryandesign (Ryan Carsten Schmidt) 9 years ago.
nawk.patch (365 bytes) - added by ryandesign (Ryan Carsten Schmidt) 9 years ago.
Portfile-c-ares.diff (468 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-c-ares.diff added

comment:1 Changed 7 years ago by tobypeterson

I'm not sure why the system awk would work, it's substantially similar to nawk. Perhaps a better approach would be to force use of a specific awk variant.

comment:2 Changed 7 years ago by tobypeterson

Resolution: worksforme
Status: newclosed

That said, this works for me with the current version of the nawk port.

comment:3 Changed 7 years ago by tobypeterson

Perhaps the parallel build fix in nawk resolved the issue.

Note: See TracTickets for help on using tickets.