From: Ulf Samuelsson <ulf@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] software FP yada yada yada
Date: Fri, 13 Oct 2006 06:44:07 +0200 [thread overview]
Message-ID: <005d01c6ee87$4beac2f0$0d68fe51@atmel.com> (raw)
In-Reply-To: 20061012231602.5DF4B353DA3@atlas.denx.de
> Dear Ulf,
>
> in message <011f01c6ee45$0eefaba0$0d68fe51@atmel.com> you wrote:
>>
>> According to the crosstool documentation at www.kegel.com:
>>
>> Most combinations of gcc 3.x.x and binutils fails when you try to build a softfloat toolchain
>> All tested combinations of gcc-4.x.x and binutils fails if softfloat is enabled.
>> If you want to use gcc 4, you cannot build u-boot as is.
>
> This is not correct. See for example ELDK 4.0: based on GCC 4.0, based
> on crosstool, and works just fine :-)
>
I quite often work with customers which has little or no experience with Linux
but still wants to start using this for new embedded systems
My goal is to have a customer download a file, decompress it and type make.
After that, everything needed to install a demo on a target should be ready.
I have choosen to use "buildroot" as the framework for this.
Buildroot will build the toolchain as part of the build process, so there is no need
to download and install a toolchain.
Avoiding extra steps like this has high value to me.
It is going to be very complicated to use buildroot with two toolchains and
there is of course nothing in buildroot which installs ELDK as the toolset.
I do want to have u-boot built as part of the buildroot make process.
Since most combinations of gcc/binutils fail it is much easier to use a
NWFPE version of the compiler also for U-boot.
>> It is worth 10s of kB to be able to use a single toolchain to build
>> u-boot, Linux and filesystem
>
> Agreed. That's how we do it with the ELDK. I don't see why this
> should be impossible for others.
>
> Best regards,
>
> Wolfgang Denk
>
Best Regards
Ulf Samuelsson ulf at atmel.com
Atmel Nordic AB
Mail: Box 2033, 174 02 Sundbyberg, Sweden
Visit: Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22 Fax +46 (8) 441 54 29
GSM +46 (706) 22 44 57
Technical support when I am not available:
AT89 C51 Applications Group: mailto:micro.hotline at nto.atmel.com
AT90 AVR Applications Group: mailto:avr at atmel.com
AT91 ARM Applications Group: mailto:at91support at atmel.com
FPSLIC Application Group: mailto:fpslic at atmel.com
Best AVR link: www.avrfreaks.net
next prev parent reply other threads:[~2006-10-13 4:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 20:00 [U-Boot-Users] software FP yada yada yada Matt Gessner
2006-10-12 20:30 ` Wolfgang Denk
2006-10-12 20:49 ` Ulf Samuelsson
2006-10-12 21:35 ` Brent Cook
2006-10-12 21:44 ` Ulf Samuelsson
2006-10-12 21:57 ` Brent Cook
2006-10-12 21:48 ` Leonid
2006-10-12 23:16 ` Wolfgang Denk
2006-10-13 4:44 ` Ulf Samuelsson [this message]
2006-10-13 7:54 ` Robert Schwebel
-- strict thread matches above, loose matches on Subject: below --
2006-10-12 20:32 Matt Gessner
2006-10-12 21:02 ` 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='005d01c6ee87$4beac2f0$0d68fe51@atmel.com' \
--to=ulf@atmel.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