Skip to content

Commit

Permalink
Use relative path in symlink
Browse files Browse the repository at this point in the history
Specifying the absolute path as the target to the symlink causes
portability problems because when we eventually archive up the result
for distribution, the absolute paths will be incorrect on the target
systems.
  • Loading branch information
Paul Groudas committed May 17, 2021
1 parent 064eaac commit 656dd4e
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion mcrouter/scripts/get_and_build_by_make.sh
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ mkdir -p "$INSTALL_DIR/lib"
# As a workaround, we just upfront link lib64 -> lib so all dependency artifacts
# end up in $INSTALL_DIR/lib which that build script *can* find.
if [ ! -e "$INSTALL_DIR/lib64" ]; then
ln -sf "$INSTALL_DIR/lib" "$INSTALL_DIR/lib64"
ln -sf lib "$INSTALL_DIR/lib64"
fi

cd "$(dirname "$0")" || ( echo "cd fail"; exit 1 )
Expand Down

0 comments on commit 656dd4e

Please sign in to comment.