libjade: fix displayed LD_LIBRARY_PATH
What changed, and why it matters
This is a tiny build-script fix. After compiling a library, the script now moves up one directory so the printed instructions about where to find the compiled files point to the correct folder. It does not change any security-sensitive code or behavior.
No security action needed; this is a benign build-helper correction.
Security signals we found
No strong security signals were identified.
Evidence from the diff
In libjade/make_libjade.sh, the build runs in a build_linux subdirectory created earlier. Before the patch, the script printed LD_LIBRARY_PATH=$PWD/build_linux/libjade while still inside build_linux, so the path would incorrectly resolve to .../build_linux/build_linux/libjade. The patch adds cd .. after make so $PWD is the project root and the displayed path becomes correct. This is purely a UI/documentation fix in a helper script.
Changed components
libjade/make_libjade.shInspect captured patch +1 / −0
diff --git a/libjade/make_libjade.sh b/libjade/make_libjade.sh
index 8f9ce3d..97b0a70 100755
--- a/libjade/make_libjade.sh
+++ b/libjade/make_libjade.sh
@@ -17,6 +17,7 @@ else
cmake -DCMAKE_BUILD_TYPE=${BUILD_TYPE} ..
fi
make -j8
+cd ..
echo "to use libjade set LD_LIBRARY_PATH=$PWD/build_linux/libjade"
if [ "${BUILD_TYPE}" == "Sanitize" ]; then
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.