Opened 5 weeks ago

Last modified 5 weeks ago

#68057 assigned defect

wren-cli @0.3.0: error: call to undeclared function 'uv__idna_toascii'

Reported by: kwolcott Owned by: herbygillot (Herby Gillot)
Priority: Normal Milestone:
Component: ports Version: 2.8.1
Keywords: ventura Cc:
Port: wren-cli

Description (last modified by ryandesign (Ryan Schmidt)) 

../../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.

Attachments (1)

wren_port_build_from_source_fails.log​ (42.2 KB) - added by kwolcott 5 weeks ago.

Download all attachments as: .zip

Change History (3)

Changed 5 weeks ago by kwolcott

Attachment: wren_port_build_from_source_fails.log​ added

comment:1 Changed 5 weeks ago by kwolcott

I initiated this process with sudo port -v -s install wren wren-cli.

Last edited 5 weeks ago by ryandesign (Ryan Schmidt) (previous) (diff)

comment:2 Changed 5 weeks ago by ryandesign (Ryan Schmidt)

Description: modified (diff)
Keywords: ventura added
Owner: set to herbygillot
Port: wren-cli added
Status: new → assigned
Summary: wren port build from source fails: call to undeclared function 'uv__idna_toascii'; → wren-cli @0.3.0: error: call to undeclared function 'uv__idna_toascii'
Version: → 2.8.1

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.

Note: See TracTickets for help on using tickets.