All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Toolchain for 0map35xx
Date: Thu, 09 Apr 2009 18:02:19 +0200	[thread overview]
Message-ID: <49DE1C0B.9060806@googlemail.com> (raw)
In-Reply-To: <B4BBC786F9164F6BB1C778A5F3223A67@Thinkpad01>

Hi Gianfranco,

Ing.G.Morandi (Portatile) wrote:
> Hello to everyone,
> 
> Few weeks ago, I've followed a thread on this list regarding the toolchain 
> should be used to compile code for omap 35xx.
> Surfing on the net, I've also found a msg of Koen Kooi where he described a 
> patch to be applied on /arch/arm/Makefile in order to let gcc 4.3.x work.
> 
> Now I am not an expert of toolchain and I didn't understand what is the 
> actual status, thus my question is:
> may I use the toolchain coming with the ELDK 4.2 to compile for omap35xx or 
> do I have to apply some patches?

I don't know toolchain coming with ELDK 4.2, but for U-Boot for OMAP 
35x you don't need a special compiler. A non-broken arm-linux-gcc or 
similar will work. While bringing OMAP U-Boot support to mainline, we 
explicitly switched to a more conservative toolchain configuration 
(-march=armv5 instead of v7a) to enable more toolchains to work.

Try the toolchain you have and ask or report errors if it doesn't work.

Best regards

Dirk

Btw.: For other code, e.g. Linux user space programs which need 
special optimizations, other toolchain might be necessary, though.

  reply	other threads:[~2009-04-09 16:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09 15:26 [U-Boot] Toolchain for 0map35xx Ing.G.Morandi
2009-04-09 16:02 ` Dirk Behme [this message]
2009-04-10 14:45   ` Ing.G.Morandi
2009-04-09 19:41 ` Wolfgang Denk

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=49DE1C0B.9060806@googlemail.com \
    --to=dirk.behme@googlemail.com \
    --cc=u-boot@lists.denx.de \
    /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.