From: Ian Campbell <icampbell@arcom.com>
To: Dave Hansen <dave@sr71.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
PPC64 External List <linuxppc64-dev@ozlabs.org>
Subject: Re: [RFC] broken installkernel.sh with CROSS_COMPILE
Date: Sat, 03 Sep 2005 09:50:20 +0100 [thread overview]
Message-ID: <1125737431.6565.88.camel@azathoth.hellion.org.uk> (raw)
In-Reply-To: <1125693554.26605.10.camel@localhost>
On Fri, 2005-09-02 at 13:39 -0700, Dave Hansen wrote:
> I noticed that my cross-compilation 'make install' broke with 2.6.13 (I
> don't use it horribly often). It's from this commit:
>
> http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0f8e2d62fa04441cd12c08ce521e84e5bd3f8a46
>
> Which added CROSS_COMPILE to each arch's install.sh:
>
> if [ -x ~/bin/${CROSS_COMPILE}installkernel ]; then exec ~/bin/${CROSS_COMPILE}installkernel "$@"; fi
>
> However, I don't just have a simple arch name as my CROSS_COMPILE, I
> have a whole path
Ah, I didn't consider that case, sorry.
> , so that line expands like this for me:
>
> + '[' -x /home/dave/bin//home/services/cross_compile/ppc64/bin/ppc64-linux-gnu-installkernel ']'
>
> Needless to say, that doesn't work :)
>
> Could we do something that's guaranteed to not have lots of extra path
> elements in it, like ARCH?
Or perhaps basename ${CROSSCOMPILE}?
Ian.
--
Ian Campbell
Campbell's Law:
Nature abhors a vacuous experimenter.
next prev parent reply other threads:[~2005-09-03 8:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-02 20:39 [RFC] broken installkernel.sh with CROSS_COMPILE Dave Hansen
2005-09-03 8:50 ` Ian Campbell [this message]
2005-09-03 12:31 ` Dave Hansen
2005-09-03 14:35 ` Ian Campbell
2005-09-07 22:35 ` linas
2005-09-07 22:53 ` Dave Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1125737431.6565.88.camel@azathoth.hellion.org.uk \
--to=icampbell@arcom.com \
--cc=dave@sr71.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox