[PATCH] Fix symbolic link to cc for targets with file extensions
Bart van der Meulen
bartvdrmeulen@gmail.com
Sun Jul 18 10:15:00 GMT 2010
Fix symbolic link to cc for targets with file extensions
When building a cross-compiler for a target which uses a file
extension of the 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>
diff -r 75197d1dacf8 -r 5754b264c657 scripts/build/cc/gcc.sh
--- a/scripts/build/cc/gcc.sh Sun Jul 18 11:18:43 2010 +0200
+++ b/scripts/build/cc/gcc.sh Sun Jul 18 11:19:29 2010 +0200
@@ -419,7 +419,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}"
--
For unsubscribe information see http://sourceware.org/lists.html#faq
More information about the crossgcc
mailing list