Re: [update] editors/neovim 0.11.0

On 2025/04/03 17:23, Laurent Cheylus wrote:
> Hi Stuart,
>
> On Thu, 3 Apr 2025 15:00:13 +0100, Stuart Henderson wrote:
>
> > On 2025/03/28 10:51, Laurent Cheylus wrote:
> >> - utf8proc library (https://github.com/JuliaStrings/utf8proc) needed to
> >> build neovim 0.11
> >> * download v2.10.0 via DIST_TUPLE * build it with cmake and install
> >> {include,lib} in ${STATIC_DEPS_INST}
> >> * set UTF8PROC_LIBRARY and UTF8PROC_INCLUDE_DIR vars for configure
> >
> > there might be a problem between this and www/netsurf/libutf8proc
>
> No issue IMHO, libutf8proc v2.10.0 library is included **statically** for neovim v0.11.
>
> On current/amd64, with my updated Neovim port:
>
> $ nvim -v
> NVIM v0.11.0
> Build type: Release
> LuaJIT 2.1.1741730670
> Run "nvim -V1 -v" for more info
>
> $ ldd $(which nvim)
> /usr/local/bin/nvim:
> Start End Type Open Ref GrpRef Name
> 00000edf92319000 00000edf929c4000 exe 2 0 0 /usr/local/bin/nvim
> 00000ee279d5a000 00000ee279e6c000 rlib 0 2 0 /usr/local/lib/libiconv.so.7.1
> 00000ee196c29000 00000ee196c3b000 rlib 0 1 0 /usr/local/lib/lua/5.1/lpeg.so
> 00000ee23c7d8000 00000ee23c809000 rlib 0 1 0 /usr/local/lib/libtree-sitter.so.5.0
> 00000ee21d476000 00000ee21d48c000 rlib 0 1 0 /usr/local/lib/libunibilium.so.1.1
> 00000ee28315f000 00000ee283183000 rlib 0 1 0 /usr/local/lib/libintl.so.8.1
> 00000ee1cc703000 00000ee1cc735000 rlib 0 1 0 /usr/lib/libm.so.10.1
> 00000ee20cf12000 00000ee20cf2b000 rlib 0 1 0 /usr/lib/libutil.so.20.0
> 00000ee1c747f000 00000ee1c748c000 rlib 0 3 0 /usr/lib/libpthread.so.27.1
> 00000ee26c6b2000 00000ee26c6fa000 rlib 0 1 0 /usr/lib/libc++abi.so.7.0
> 00000ee1b00f1000 00000ee1b0125000 rlib 0 1 0 /usr/local/lib/libuv.so.5.1
> 00000ee2703a4000 00000ee2704ab000 rlib 0 1 0 /usr/lib/libc.so.100.3
> 00000ee242533000 00000ee242533000 ld.so 0 1 0 /usr/libexec/ld.so
>
> I chose not to update and use www/netsurf/libutf8proc port because it's a specific dependency for www/netsurf port (by the way, very outdated, last update = August 2019).
>
> Laurent
>

You still need to be careful even if it's statically linked. In
particular you need to make sure that it can't accidentally pick up
anything from /usr/local/{include,lib} if present at build time.
Especially considering what Laurie reported.