# HG changeset patch
# User Bart vdr. Meulen <bartvdrmeulen@gmail.com>
# Date 1279574162 -7200
# Node ID 471acb219d7758400772c3be486e1176ac5cdead
# Parent  42d702fd5dd109b0d0c33022c6387214cf832370
complibs: fix using static companion libraries

When building a cross-compiler for a target which uses a file extension for
binaries the symbolic link to cc is not created correctly because the lookup
of the gcc binary is done in a incorrect path

Signed-off-by: Bart vdr. Meulen <bartvdrmeulen@gmail.com>
(transplanted from 3917f2dafed1bb189e39f50e8506b3141926d7e1)

diff -r 42d702fd5dd1 -r 471acb219d77 scripts/build/cc/gcc.sh
--- a/scripts/build/cc/gcc.sh	Thu Jul 15 22:34:31 2010 +0200
+++ b/scripts/build/cc/gcc.sh	Mon Jul 19 23:16:02 2010 +0200
@@ -396,7 +396,7 @@
     # Create a symlink ${CT_TARGET}-cc to ${CT_TARGET}-gcc to always be able
     # to call the C compiler with the same, somewhat canonical name.
     # check whether compiler has an extension
-    file="$( ls -1 "${CT_TARGET}/bin/${CT_TARGET}-gcc."* 2>/dev/null || true )"
+    file="$( ls -1 "${CT_PREFIX_DIR}/bin/${CT_TARGET}-gcc."* 2>/dev/null || true )"
     [ -z "${file}" ] || ext=".${file##*.}"
     CT_DoExecLog ALL ln -sv "${CT_TARGET}-gcc${ext}" "${CT_PREFIX_DIR}/bin/${CT_TARGET}-cc${ext}"