scripts: hack-in lib32->lib symlinks
author"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Fri Sep 10 12:14:24 2010 +0200 (2010-09-10)
changeset 211675ee9a87c0e4
parent 2115 e565ce1ef492
child 2117 24aacb93191d
scripts: hack-in lib32->lib symlinks

Some archs (eg. ppc64 with n32 ABI) will install their
variants in lib32/ instead of lib/, so do for lib32 as
we do for lib64->lib symlinks.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
scripts/crosstool-NG.sh.in
     1.1 --- a/scripts/crosstool-NG.sh.in	Fri Sep 10 13:23:58 2010 +0200
     1.2 +++ b/scripts/crosstool-NG.sh.in	Fri Sep 10 12:14:24 2010 +0200
     1.3 @@ -331,11 +331,19 @@
     1.4      # Now, in case we're 64 bits, just have lib64/ be a symlink to lib/
     1.5      # so as to have all libraries in the same directory (we can do that
     1.6      # because we are *not* multilib).
     1.7 +    # Mips64 with n32 emulation install its libs in lib32, so also prepare
     1.8 +    # these symlinks
     1.9 +    # Not all the symlinks are necessary, but better safe than sorry...
    1.10      if [ "${CT_ARCH_64}" = "y" ]; then
    1.11 -        CT_DoExecLog ALL ln -sf "lib" "${CT_PREFIX_DIR}/lib64"
    1.12 -        CT_DoExecLog ALL ln -sf "lib" "${CT_SYSROOT_DIR}/lib64"
    1.13 -        CT_DoExecLog ALL ln -sf "lib" "${CT_SYSROOT_DIR}/usr/lib64"
    1.14 -        CT_DoExecLog ALL ln -sf "lib" "${CT_PREFIX_DIR}/${CT_TARGET}/lib64"
    1.15 +        for d in                            \
    1.16 +            "${CT_PREFIX_DIR}"              \
    1.17 +            "${CT_SYSROOT_DIR}"             \
    1.18 +            "${CT_SYSROOT_DIR}/usr"         \
    1.19 +            "${CT_PREFIX_DIR}/${CT_TARGET}" \
    1.20 +        ; do
    1.21 +            CT_DoExecLog ALL ln -sf "lib" "${d}/lib32"
    1.22 +            CT_DoExecLog ALL ln -sf "lib" "${d}/lib64"
    1.23 +        done
    1.24      fi
    1.25  
    1.26      # Determine build system if not set by the user