mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Greg KH <greg@kroah.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: arm + sh cross compile suite for amd64 (i386)?
Date: Mon, 7 Aug 2006 15:23:38 -0700	[thread overview]
Message-ID: <20060807152338.1307e631.akpm@osdl.org> (raw)
In-Reply-To: <20060807210625.GB14327@mars.ravnborg.org>

On Mon, 7 Aug 2006 23:06:25 +0200
Sam Ravnborg <sam@ravnborg.org> wrote:

> On Mon, Aug 07, 2006 at 11:02:09PM +0200, Sam Ravnborg wrote:
>  
> > So for sh I would expect the following is a better fix:
> 
> Reminds me. Anyone has a pointer to arm+sh gcc + binutils cross-compile
> suite that can run on my amd64 box?
> My usual source: http://developer.osdl.org/dev/plm/cross_compile/
> did have neither sh nor arm :-(
> 

I was somewhat-successful in building those up.  From my notes:

arm:
	eval `cat arm.dat gcc-3.4.5-glibc-2.3.6.dat` sh all.sh --notest

sh4:
	eval `cat sh4.dat gcc-3.4.5-glibc-2.3.6.dat` sh all.sh --notest

when you've struggled with crosstool for long enough, that'll become
meaningful ;)


fwiw, I've uploaded x86 binaries to http://userweb.kernel.org/~akpm/. 
They're a bit flakey but seem to be good enough to get through a defconfig
build.  The main problem is fancy machine-specific binutils options which
are present in the kernel Makefiles but which stock binutils doesn't know
about.



  reply	other threads:[~2006-08-07 22:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-07 19:27 [GIT PATCH] kbuild fixes for 2.6.18 Sam Ravnborg
2006-08-07 20:42 ` Greg KH
2006-08-07 21:02   ` Sam Ravnborg
2006-08-07 21:06     ` arm + sh cross compile suite for amd64 (i386)? Sam Ravnborg
2006-08-07 22:23       ` Andrew Morton [this message]
2006-08-07 21:20     ` [GIT PATCH] kbuild fixes for 2.6.18 Greg KH
2006-08-08  8:45     ` Takashi Iwai

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=20060807152338.1307e631.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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

all inboxes | Powered by JetHome®