@@ -74,8 +74,8 @@ PACKAGECONFIG ??= "ares brotli icu zlib"
PACKAGECONFIG[ares] = "--shared-cares,,c-ares c-ares-native"
PACKAGECONFIG[brotli] = "--shared-brotli,,brotli brotli-native"
PACKAGECONFIG[icu] = "--with-intl=system-icu,--without-intl,icu icu-native"
-PACKAGECONFIG[libuv] = "--shared-libuv,,libuv"
-PACKAGECONFIG[nghttp2] = "--shared-nghttp2,,nghttp2"
+PACKAGECONFIG[libuv] = "--shared-libuv,,libuv libuv-native"
+PACKAGECONFIG[nghttp2] = "--shared-nghttp2,,nghttp2 nghttp2-native"
PACKAGECONFIG[shared] = "--shared"
PACKAGECONFIG[zlib] = "--shared-zlib,,zlib"
In case nghttp2 and/or libuv PACKAGECONFIGs are enabled, nodejs will build some binaries for the build system also, linking to native binaries and using headers from the native sysroot. However in case the dependencies are missing from the native sysroot, then it falls back to the build system's sysroot, and use the files that it can find there. If the build system doesn't have nghttp2/libuv installed, then compilation fails: libuv: ../tools/executable_wrapper.h:5:10: fatal error: uv.h: No such file or directory ngtthp2: <...snip...>/build/tmp/hosttools/ld: cannot find -lnghttp2: No such file or directory To avoid falling back to the build system's sysroot, add the missing libuv-native and nghttp2-native dependencies. Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com> --- meta-oe/recipes-devtools/nodejs/nodejs_22.22.0.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)