From: Daniel Kegel <dank@kegel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: Single ARM Toolchain?
Date: Mon, 10 May 2004 15:41:16 -0700 [thread overview]
Message-ID: <40A0050C.8040005@kegel.com> (raw)
In-Reply-To: <20040510221009.50689.qmail@web14811.mail.yahoo.com>
Allen Curtis wrote:
> I have created several versions of ARM cross-compiler
> toolchains but have not discovered a configuration
> that works with both "u-boot" and Linux 2.6.
>
> Using crosstool-0.27:
> GCC 2.95.3, BINUTILS 2.14.90.0.8, GLIBC 2.2.5 - builds
> the Linux kernel but not U-Boot
>
> GCC 2.95.3, BINUTILS 2.11.2, GLIBC 2.1.3 - builds
> U-Boot but not 2.6 Linux kernel (.incbin support)
>
> The newest GCC I can build on my system is 3.2 since
> my host compiler is 2.96.
>
> I have searched the archives and found that this is a
> common question. Unfortunately I did not find a
> definitive answer.
Can you post the errors?
(btw, crosstool-0.27 had some arm issues,
and crosstool-0.28-rc13 has the vfp printf patch,
but I'm not sure those matter for this.)
- Dan
next prev parent reply other threads:[~2004-05-10 22:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 22:10 [U-Boot-Users] Single ARM Toolchain? Allen Curtis
2004-05-10 22:41 ` Daniel Kegel [this message]
2004-05-10 23:20 ` Wolfgang Denk
2004-05-11 14:10 ` Allen Curtis
2004-05-11 16:06 ` 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=40A0050C.8040005@kegel.com \
--to=dank@kegel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox