All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave@sr71.net>
To: linas <linas@austin.ibm.com>
Cc: icampbell@arcom.com,
	PPC64 External List <linuxppc64-dev@ozlabs.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] broken installkernel.sh with CROSS_COMPILE
Date: Wed, 07 Sep 2005 15:53:51 -0700	[thread overview]
Message-ID: <1126133631.6354.2.camel@localhost> (raw)
In-Reply-To: <20050907223538.GF30028@austin.ibm.com>

On Wed, 2005-09-07 at 17:35 -0500, linas wrote:
> On Fri, Sep 02, 2005 at 01:39:13PM -0700, Dave Hansen was heard to remark:
> > 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:
> > 
> > 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, so that line expands like this for me:
> 
> Try this:
> 
> # path to compilers and binutils, user may override by setting
> # CROSS_PATH in environment
> CROSS_PATH=${CROSS_PATH:-/opt/cross-3.3.2/bin}
> 
> CROSS_COMPILE=powerpc64-linux-
> 
> export PATH=$CROSS_PATH:$PATH
> 
> echo "using toolchain from $CROSS_PATH"

I'm not sure I understand.  Where should that be done?

-- Dave


      reply	other threads:[~2005-09-07 22:53 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
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 [this message]

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=1126133631.6354.2.camel@localhost \
    --to=dave@sr71.net \
    --cc=icampbell@arcom.com \
    --cc=linas@austin.ibm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.