On 15.12.2021 10:52, Edd Barrett wrote:
Hi,
Here's an update to libuv, needed for neovim-0.6.0 (requires new functions
recently introduced in libuv).
There are three more test failures than before:
```
--- failing-before Wed Dec 15 09:18:34 2021
+++ failing-after Wed Dec 15 09:18:46 2021
@@ -1,4 +1,7 @@
fs_lutime
get_currentexe
+tcp_close_while_connecting
+tcp_connect_timeout
udp_connect
udp_multicast_join
+udp_send_hang_loop
```
(Before there were 4 failures, now there are 7).
I'll report all of the failures upstream shortly, but hopefully they are not
blockers to the update. The majority of the suite passes.
I've done a major bump, since diffing the T symbols in old and new shared
object suggests that public symbols have been removed. The affected symbols are
not exported in headers, but you never know what code in the wild might be
doing.
I've done a build test of all ports which build depend on libuv on amd64 (using
dpb):
```
sqlite> select fullpkgpath from ports where lib_depends like '%%libuv%%';
devel/cmake
x11/mruby-zest
devel/radare2/main
devel/py-uv,python3
editors/neovim
lang/hashlink
lang/moarvm
www/h2o
net/isc-bind
net/isc-bind,geoip
net/usockets
www/h2o,mruby
```
Nothing failed to build.
I'm definitely looking for OKs for this, as I don't want to be responsible for
breaking cmake!
Any comments or OKs?
--
Best Regards
Edd Barrett
https://www.theunixzoo.co.uk
Edd,
Thanks for this! I heard there were hackers at work... delivered so
quick! Now neovim is building with diff from paco@
Diff applied, make, make install. amd64. OK here.
I've built devel/cmake, devel/radare2, and editors/neovim as I work with
all three of them often enough. I will put them through paces. Not sure
I have bandwidth to look into what specifics may apply to the bump.
Thanks!
--
Evan
