path: root/arch/arm/boot/
diff options
authorIan Campbell <>2005-06-23 00:08:10 -0700
committerLinus Torvalds <>2005-06-23 09:45:07 -0700
commit0f8e2d62fa04441cd12c08ce521e84e5bd3f8a46 (patch)
tree74c607e8766d23b3573afced1f20272978a42133 /arch/arm/boot/
parentd0e7feb03d5ac48069c2fd57bbba61522e0ca493 (diff)
[PATCH] use ${CROSS_COMPILE}installkernel in arch/*/boot/
The attached patch causes the various arch specific scripts to look for ${CROSS_COMPILE}installkernel rather than just installkernel (in both /sbin/ and ~/bin/ where the script already did this). This allows you to have e.g. arm-linux-installkernel as a handy way to install on your cross target. It also prevents the script picking up on the host /sbin/installkernel which causes the script to fall through and do the install itself (which is what I actually use myself, with $INSTALL_PATH set). I don't believe it causes back-compatibility problems since calling the host installkernel was never likely to work or be what you wanted when cross compiling anyway. If $CROSS_COMPILE isn't set then nothing changes. I only use ARM and i386 myself but I figured it couldn't hurt to do the whole lot. I've cc'd those who I hope are the arch maintainers for files that I've touched. Signed-off-by: Ian Campbell <> Signed-off-by: Andrew Morton <> Signed-off-by: Linus Torvalds <>
Diffstat (limited to 'arch/arm/boot/')
1 files changed, 2 insertions, 2 deletions
diff --git a/arch/arm/boot/ b/arch/arm/boot/
index 935bb27369e9..9f9bed207345 100644
--- a/arch/arm/boot/
+++ b/arch/arm/boot/
@@ -21,8 +21,8 @@
# User may have a custom install script
-if [ -x ~/bin/installkernel ]; then exec ~/bin/installkernel "$@"; fi
-if [ -x /sbin/installkernel ]; then exec /sbin/installkernel "$@"; fi
+if [ -x ~/bin/${CROSS_COMPILE}installkernel ]; then exec ~/bin/${CROSS_COMPILE}installkernel "$@"; fi
+if [ -x /sbin/${CROSS_COMPILE}installkernel ]; then exec /sbin/${CROSS_COMPILE}installkernel "$@"; fi
if [ "$(basename $2)" = "zImage" ]; then
# Compressed install