From 7bf391ce6150e43b039d9ba499df68e72e5725bb Mon Sep 17 00:00:00 2001 From: James Turner Date: Thu, 8 Feb 2018 11:16:49 -0300 Subject: Unset Conda's LD_RUN_PATH when building external IRAF packages, 1. to avoid patchelf warnings, 2. because they don't actually need an RPATH and 3. because I think I have seen problems with patchelf + IRAF in the past (with Ureka). Disabling "binary_relocation" in meta.yaml is insufficient to avoid an RPATH being set (and actually makes things worse by leaving an absolute RPATH instead of a relative one, which later gets updated differently for each env by conda, breaking hard linking between the envs, with a lot of wasted disk space). --- scripts/ac_build_iraf_pkg | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/ac_build_iraf_pkg b/scripts/ac_build_iraf_pkg index 0428078..b1dac6f 100755 --- a/scripts/ac_build_iraf_pkg +++ b/scripts/ac_build_iraf_pkg @@ -34,7 +34,7 @@ if [ -z "$iraf" -o -z "$IRAFARCH" ]; then fi # These conda-set variables could interfere with building IRAF packages: -unset ARCH CFLAGS CXXFLAGS LDFLAGS MACOSX_DEPLOYMENT_TARGET +unset ARCH CFLAGS CXXFLAGS LDFLAGS LD_RUN_PATH MACOSX_DEPLOYMENT_TARGET # Create any new dirs & files with the expected permissions: umask 022 -- cgit