Building Node with shared libuv doesn't work with the given `--shared-libuv-path`

[geeksilva97]

Version

v25.0.0-pre

Platform

Darwin LM-JNVH7RPW6J 23.6.0 Darwin Kernel Version 23.6.0: Thu Mar  6 22:00:07 PST 2025; root:xnu-10063.141.1.704.6~1/RELEASE_ARM64_T6030 arm64

Subsystem

build

What steps will reproduce the bug?

Configure node with

./configure --shared-libuv \
  --shared-libuv-includes=/home/libuv/include \
  --shared-libuv-libpath=/home/libuv/.libs

Compile node

make

It compiles but gets shared lib from /usr/local/lib/libuv.1.dylib as we can see using otool. After compiling

> otool -L ./node
./node:
	/usr/local/lib/libuv.1.dylib (compatibility version 2.0.0, current version 2.0.0)
	/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 3208.0.0)
	/System/Library/Frameworks/Security.framework/Versions/A/Security (compatibility version 1.0.0, current version 61439.60.117)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1800.105.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1351.0.0)

How often does it reproduce? Is there a required condition?

Always

What is the expected behavior? Why is that the expected behavior?

From my understanding, it should get from /home/libuv/.libs/libuv.1dylib since that's the path I provided in the --shared-libuv option

What do you see instead?

It's getting from /usr/local/lib/libuv.1.dylib

Additional information

No response

[aduh95]

What does file /home/libuv/.libs/libuv.1dylib output?

[bnoordhuis]

Another thing to consider: --shared-libuv-libpath=/home/libuv/.libs adds -L/home/libuv/.libs to the linker flags. If the linker searches /usr/local/lib before /home/libuv/.libs, then it's going to pick the one you don't want.

[geeksilva97]

What does file /home/libuv/.libs/libuv.1dylib output?

/home/libuv/.libs/libuv.1.dylib: Mach-O 64-bit dynamically linked shared library arm64

The output is the same for /usr/local/lib/libuv.1.dylib.

[geeksilva97]

Another thing to consider: --shared-libuv-libpath=/home/libuv/.libs adds -L/home/libuv/.libs to the linker flags. If the linker searches /usr/local/lib before /home/libuv/.libs, then it's going to pick the one you don't want.

That makes sense, @bnoordhuis . I have a question: shouldn't the path given with --shared-libuv-libpath be put in front? Before the other paths?

I compiled a side libuv project I have with:

gcc -L/home/libuv/.libs -luv -v main.c -o main

The ld command was like

"/Library/Developer/CommandLineTools/usr/bin/ld" -demangle -lto_library /Library/Developer/CommandLineTools/usr/lib/libLTO.dylib -no_deduplicate -dynamic -arch arm64 -platform_version macos 14.0.0 15.2 -syslibroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk -mllvm -enable-linkonceodr-outlining -o main -L/home/libuv/.libs -L/usr/local/lib -luv /var/folders/k6/r2k8052j3pjbmqs96wws8km00000gn/T/main-eb19ff.o -lSystem /Library/Developer/CommandLineTools/usr/lib/clang/16/lib/darwin/libclang_rt.osx.a

The order was

• -L/home/libuv/.libs
• -L/usr/local/lib

I expected Node to be compiled in the same way when using shared libuv. Does that make any sense?