Mercurialcrosstool-ng / changeset
summary | shortlog | changelog | graph | tags | branches | files | changeset | raw | bz2 | help
complibs: fix using static companion libraries 1.7
authorBart vdr. Meulen <bartvdrmeulen@gmail.com>
Mon Jul 19 23:16:02 2010 +0200 (2010-07-19)
branch1.7
changeset 2046471acb219d77
parent 2035 42d702fd5dd1
child 2047 ace1d90c9b15
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)
scripts/build/cc/gcc.sh file | annotate | diff | revisions 
     1.1 --- a/scripts/build/cc/gcc.sh	Thu Jul 15 22:34:31 2010 +0200
     1.2 +++ b/scripts/build/cc/gcc.sh	Mon Jul 19 23:16:02 2010 +0200
     1.3 @@ -396,7 +396,7 @@
     1.4      # Create a symlink ${CT_TARGET}-cc to ${CT_TARGET}-gcc to always be able
     1.5      # to call the C compiler with the same, somewhat canonical name.
     1.6      # check whether compiler has an extension
     1.7 -    file="$( ls -1 "${CT_TARGET}/bin/${CT_TARGET}-gcc."* 2>/dev/null || true )"
     1.8 +    file="$( ls -1 "${CT_PREFIX_DIR}/bin/${CT_TARGET}-gcc."* 2>/dev/null || true )"
     1.9      [ -z "${file}" ] || ext=".${file##*.}"
    1.10      CT_DoExecLog ALL ln -sv "${CT_TARGET}-gcc${ext}" "${CT_PREFIX_DIR}/bin/${CT_TARGET}-cc${ext}"
    1.11
crosstool-ng