summaryrefslogtreecommitdiff
path: root/otp_build
diff options
context:
space:
mode:
authorAlexey Lebedeff <alebedev@mirantis.com>2016-04-21 18:11:58 +0300
committerAlexey Lebedeff <alebedev@mirantis.com>2016-04-21 18:45:23 +0300
commit98b8650d22e94a5ff839170833f691294f6276d0 (patch)
treea2efdc4e9fb8e072a4d7604d8661745bf4c2b7b6 /otp_build
parent523e048754f5086a6cc4fd9a250e1b495fc5b9b8 (diff)
downloaderlang-98b8650d22e94a5ff839170833f691294f6276d0.tar.gz
Fix program paths used in build process
Not every OS has '/bin/rm' or '/bin/pwd' at exactly that location. In some places in configure scripts result of AC_PATH_PROG was already correctly used, this patch makes this usage more consistent. As for `/bin/pwd` in `otp_build`, shell built-in one is already used in mingw parts - so it should cause no harm to use it everywhere. Difference is only in symlinks resolution - non-builtin `pwd` always returns absolute path, and builtin-one could take into account what sequence of user actions lead to current value of $PWD.
Diffstat (limited to 'otp_build')
-rwxr-xr-xotp_build4
1 files changed, 2 insertions, 2 deletions
diff --git a/otp_build b/otp_build
index ac99ced42a..86ae804c3e 100755
--- a/otp_build
+++ b/otp_build
@@ -139,7 +139,7 @@ check_erltop ()
if [ "X$ERL_TOP" = "X" ]; then
if [ -f ./otp_build -a -f ./erts/autoconf/config.guess ]; then
ERLTOP_FORCED=true
- ERL_TOP=`/bin/pwd`
+ ERL_TOP=`pwd`
export ERL_TOP
else
echo "The environment variable ERL_TOP must be set." >&2
@@ -679,7 +679,7 @@ echo_env_erltop ()
if [ X"$ERL_TOP" = X"" -o "$ERLTOP_FORCED" = "true" ]; then
if [ -f ./otp_build ]; then
# Seems to be current directory...
- echo_setenv ERL_TOP `/bin/pwd` ';'
+ echo_setenv ERL_TOP `pwd` ';'
else
echo "You need to either set ERL_TOP first or stand in the same" \
"directory as this script resides in." >&2