public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Alex Chiang <achiang@hp.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Robin Holt <holt@sgi.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-ia64@vger.kernel.org
Subject: Re: cross-compilers
Date: Thu, 9 Apr 2009 14:52:37 +0200	[thread overview]
Message-ID: <20090409125237.GD7921@lug-owl.de> (raw)
In-Reply-To: <20090408173332.GB20187@ldl.fc.hp.com>

[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]

On Wed, 2009-04-08 11:33:32 -0600, Alex Chiang <achiang@hp.com> wrote:
> * Andrew Morton <akpm@linux-foundation.org>:
> > On Tue, 7 Apr 2009 23:46:12 -0600 Alex Chiang <achiang@hp.com> wrote:
> > > * Robin Holt <holt@sgi.com>:
> > > > Don't know if this answers your problem, but I use the tools from
> > > > emdebian and they do not suffer from the problems you list below.
> > > 
> > > Wow, this seems _much_ simpler. Once you get the toolchain
> > > installed, all you have to do is set ARCH and CROSS_COMPILE
> > > appropriately?
> > > 
> > > I guess the question remains for Andrew. Since I pretty much did
> > > all the work needed to update his cross-compiler repo, is there
> > > still value in it?
> > 
> > We would benefit very much from having someone who actually maintains a
> > suite of cross-compilers for kernel developers.
>  
> Ok, I'll work with Vegard on this.

Is anybody building GCC trunk for the targets on a daily basis? I do
build vax-linux (kernel-only) cross compilers quite often and the
build script could probably also handle other targets.

MfG, JBG

-- 
      Jan-Benedict Glaw      jbglaw@lug-owl.de              +49-172-7608481
  Signature of:                        Lauf nicht vor Deinem Glück davon:
  the second  :                             Es könnte hinter Dir stehen!

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2009-04-09 13:00 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08  0:39 cross-compilers Alex Chiang
2009-04-08  1:03 ` cross-compilers Robin Holt
2009-04-08  5:46   ` cross-compilers Alex Chiang
2009-04-08  5:53     ` cross-compilers Pekka Enberg
2009-04-08  5:54     ` cross-compilers Andrew Morton
2009-04-08  6:12       ` cross-compilers Peter Chubb
2009-04-08 10:53       ` cross-compilers Matthew Wilcox
2009-04-08 15:29       ` cross-compilers Lennart Sorensen
2009-04-08 15:39       ` cross-compilers Xavier Bestel
2009-04-08 17:33       ` cross-compilers Alex Chiang
2009-04-08 17:36         ` cross-compilers Randy Dunlap
2009-04-09 12:52         ` Jan-Benedict Glaw [this message]
2009-04-09 20:51           ` cross-compilers Segher Boessenkool
2009-04-09  0:20       ` cross-compilers Rob Landley
2009-04-09  0:33       ` cross-compilers Tony Breeds
2009-04-09  0:44         ` cross-compilers Andrew Morton
2009-04-09  0:55           ` cross-compilers Alex Chiang
2009-04-09 20:24             ` cross-compilers Helge Deller
2009-04-09 20:31               ` cross-compilers Alex Chiang
2009-04-09 21:52           ` cross-compilers Tony Breeds
2009-04-09 23:47             ` cross-compilers Jan-Benedict Glaw
2009-04-10 10:12               ` cross-compilers Jan-Benedict Glaw
2009-04-10 10:19                 ` cross-compilers Mike Frysinger
2009-04-10 10:49                   ` cross-compilers Sam Ravnborg
2009-04-10 10:50                     ` cross-compilers Mike Frysinger
2009-04-10 15:59                     ` cross-compilers Jan-Benedict Glaw
2009-04-10 16:03                       ` cross-compilers Al Viro
2009-04-11 11:23                     ` cross-compilers Jan-Benedict Glaw
2009-04-10  5:45             ` cross-compilers Sam Ravnborg
2009-04-11  9:46               ` cross-compilers Tony Breeds
2009-04-09  7:29         ` cross-compilers Geert Uytterhoeven
2009-04-08  5:55     ` cross-compilers Robin Holt
2009-04-08  9:50     ` cross-compilers Andi Kleen
2009-04-08 11:08 ` cross-compilers Alex Buell

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=20090409125237.GD7921@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=achiang@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=holt@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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