diff options
| author | Ian Campbell <icampbell@arcom.com> | 2005-06-23 09:08:10 +0200 |
|---|---|---|
| committer | Linus Torvalds <torvalds@ppc970.osdl.org> | 2005-06-23 18:45:07 +0200 |
| commit | 0f8e2d62fa04441cd12c08ce521e84e5bd3f8a46 (patch) | |
| tree | 74c607e8766d23b3573afced1f20272978a42133 /arch/i386/lib/dec_and_lock.c | |
| parent | [PATCH] biarch compiler support for i386 (diff) | |
| download | linux-0f8e2d62fa04441cd12c08ce521e84e5bd3f8a46.tar.xz linux-0f8e2d62fa04441cd12c08ce521e84e5bd3f8a46.zip | |
[PATCH] use ${CROSS_COMPILE}installkernel in arch/*/boot/install.sh
The attached patch causes the various arch specific install.sh 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 <icampbell@arcom.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'arch/i386/lib/dec_and_lock.c')
0 files changed, 0 insertions, 0 deletions