[MacPorts] #68057: wren-cli @0.3.0: error: call to undeclared function 'uv__idna_toascii' (was: wren port build from source fails: call to undeclared function 'uv__idna_toascii'; )

[MacPorts]

#68057: wren-cli @0.3.0: error: call to undeclared function 'uv__idna_toascii'
-----------------------+-------------------------
  Reporter:  kwolcott  |      Owner:  herbygillot
      Type:  defect    |     Status:  assigned
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:  2.8.1
Resolution:            |   Keywords:  ventura
      Port:  wren-cli  |
-----------------------+-------------------------
Changes (by ryandesign):

 * status:  new => assigned
 * keywords:   => ventura
 * version:   => 2.8.1
 * owner:  (none) => herbygillot
 * port:   => wren-cli


Old description:

> ../../deps/libuv/src/unix/getaddrinfo.c:165:10: error: call to undeclared
> function 'uv__idna_toascii'; ISO C99 and later do not support implicit
> function declarations [-Wimplicit-function-declaration]
>     rc = uv__idna_toascii(hostname,
>          ^
> 1 error generated.

New description:

 {{{
 ../../deps/libuv/src/unix/getaddrinfo.c:165:10: error: call to undeclared
 function 'uv__idna_toascii'; ISO C99 and later do not support implicit
 function declarations [-Wimplicit-function-declaration]
     rc = uv__idna_toascii(hostname,
          ^
 1 error generated.
 }}}

--

Comment:

 Remember WikiFormatting and see WimplicitFunctionDeclaration.

 I see that the problem is in a bundled copy of libuv 1.34.2 and this makes
 me wonder if the port could avoid the problem by using the MacPorts copy
 of libuv 1.44.2 instead which would be preferable for other reasons as
 well.

 I do not see this issue on my Monterey x86_64 system and we did not see
 the problem on our buildbot machines. I do see a similar report from a
 Ventura x86_64 user in another program that bundles libuv:

 https://github.com/pytorch/pytorch/issues/101586

 wren-cli 0.4.0 was released nearly two years ago and it updates the
 bundled libuv to 1.38.0. The port should be updated; maybe it fixes this
 problem.

-- 
Ticket URL: <https://trac.macports.org/ticket/68057#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS