All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: hkh@cypress.com
Cc: Linux-omap-open-source@linux.omap.com
Subject: Re: Building kenel error
Date: Fri, 18 Aug 2006 20:50:23 +0200	[thread overview]
Message-ID: <44E60BEF.2090507@gmail.com> (raw)
In-Reply-To: <1155918292.2949.25.camel@localhost.localdomain>

Hingkwan Huen wrote:
> Which version of tool chain are
> you using for 2.6.16 or 2.6.17 kernel?

Regarding GCC 4.x.x, if you like prebuild toolchain, try 
CodeSourcery:

http://www.codesourcery.com/gnu_toolchains/arm/

If you like to build your toolchain on our own, try crosstool:

http://kegel.com/crosstool/

crosstool-0.42 with

eval `cat arm.dat gcc-4.1.0-glibc-2.3.2.dat`  sh all.sh --notest

configuration and additional patch (for ALSA sound)

http://gcc.gnu.org/viewcvs/branches/csl/sourcerygxx-4_1/gcc/cse.c?r1=115616&r2=115615&view=patch&pathrev=115616
(fixes http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27363)

works for me.

There may be several other working GCC 4.x.x toolchains out 
there. But I think most people still use GCC 3.x.x toolchains.

Dirk

  reply	other threads:[~2006-08-18 18:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-18 12:04 Building kenel error Woodruff, Richard
2006-08-18 16:24 ` Hingkwan Huen
2006-08-18 18:50   ` Dirk Behme [this message]
2006-08-29 10:43 ` Building kenel error (uImage) kabbin
2006-08-29 11:13   ` imre.deak
2006-08-30 10:15   ` kabbin
  -- strict thread matches above, loose matches on Subject: below --
2006-08-18 20:33 Building kenel error Woodruff, Richard
2006-08-18 20:26 Woodruff, Richard
2006-08-18 18:56 Woodruff, Richard
2006-08-18 20:15 ` Brian Swetland
2006-08-18 20:29 ` lamikr
2006-08-18  9:18 kabbin
2006-08-15  9:47 kabbin

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=44E60BEF.2090507@gmail.com \
    --to=dirk.behme@googlemail.com \
    --cc=Linux-omap-open-source@linux.omap.com \
    --cc=hkh@cypress.com \
    /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.