linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: Alex Chiang <achiang@hp.com>,
	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 22:51:38 +0200	[thread overview]
Message-ID: <1D6A3AE1-14BE-491F-89F2-BC9CE04F444E@kernel.crashing.org> (raw)
In-Reply-To: <20090409125237.GD7921@lug-owl.de>

> Is anybody building GCC trunk for the targets on a daily basis?

Not daily yet, but often anyway.  Also binutils and kernel mainline.

Scripts: <http://git.infradead.org/users/segher/buildall.git>

Edit "config" for your local paths etc.
Run  ./build [--kernel] <arch> [<some-defconfig>]  to build a toolchain
and a kernel, or only the kernel if --kernel is given.  Run  ./buildall
to build a toolchain+kernel for all archs.


Segher


  reply	other threads:[~2009-04-09 20:49 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         ` cross-compilers Jan-Benedict Glaw
2009-04-09 20:51           ` Segher Boessenkool [this message]
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=1D6A3AE1-14BE-491F-89F2-BC9CE04F444E@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=achiang@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=holt@sgi.com \
    --cc=jbglaw@lug-owl.de \
    --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;
as well as URLs for NNTP newsgroup(s).