Roman Kyrylych wrote:
2008/7/22 <silvio@port1024.net--thread>:
From: Silvio fricke <silvio@port1024.net>
In most cross-compile environment there is a environment-variable $CROSS_COMPILE which reflects the toolchain.
Signed-off-by: Silvio fricke <silvio@port1024.net> --- scripts/makepkg.sh.in | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in index 2777102..9292b1b 100644 --- a/scripts/makepkg.sh.in +++ b/scripts/makepkg.sh.in @@ -736,11 +736,11 @@ tidy_install() { find ${bindirs} -type f 2>/dev/null | while read binary ; do case "$(file -biz "$binary")" in *application/x-sharedlib*) # Libraries (.so) - /usr/bin/strip --strip-debug "$binary";; + ${CROSS_COMPILE}strip --strip-debug "$binary";; *application/x-archive*) # Libraries (.a) - /usr/bin/strip --strip-debug "$binary";; + ${CROSS_COMPILE}strip --strip-debug "$binary";; *application/x-executable*) # Binaries - /usr/bin/strip "$binary";; + ${CROSS_COMPILE}strip "$binary";; esac done fi
As far as I understand this - when CROSS_COMPILE is not set (most not-cross-compile environments) - strip will require correct $PATH, which is bad (that's why full paths are always used).
What is the deal with this CROSS_COMPILE env var anyway? I never heard about it before. And it really only needs to be used in that place?