public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Chiang <achiang@hp.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, linux-ia64@vger.kernel.org
Subject: cross-compilers
Date: Tue, 7 Apr 2009 18:39:21 -0600	[thread overview]
Message-ID: <20090408003921.GA5054@ldl.fc.hp.com> (raw)

Hi Andrew,

I've been using your cross-compilers here:

	http://userweb.kernel.org/~akpm/cross-compilers/

for a long time now, but they're starting to suffer from a bit of
neglect.

For example, the ia64 bundle, which used gcc 3.4.5 is now finally
too old to build 2.6.30-rc1, because of a gcc bug related to
labels.

Some of the newer bundles which use gcc 4.1.0 don't work because
of a check in:

	include/linux/compiler-gcc4.h

So my question is, do you still use those tools hosted on
kernel.org or do you have a new solution these days?

If you have a new solution, I'd like to hear it, because I found
those cross-compilers pretty useful, as I'm sure others did.

I spent most of yesterday fiddling about and managed to build an
x86_64 host, ia64 target, gcc 4.2.3, glibc 2.3.6 bundle, and it
all seems to work.

Is this something you're interested in? I could send you my
tarball (and slowly work on some of the other archs).

If so, what were the crosstool build options you used? I'm
specifically wondering about:

	- should I am for lowest common denominator host or are
	  you ok with x86_64 host
	
	- did you statically link the toolchain? or is it
	  dynamically linked?

Thanks.

/ac


             reply	other threads:[~2009-04-08  0:39 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08  0:39 Alex Chiang [this message]
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           ` 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=20090408003921.GA5054@ldl.fc.hp.com \
    --to=achiang@hp.com \
    --cc=akpm@linux-foundation.org \
    --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