From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] static libgcc_s
Date: Thu, 1 Mar 2007 07:13:40 +0100 [thread overview]
Message-ID: <004901c75bcc$356388c0$8c1d10ac@atmel.com> (raw)
In-Reply-To: 45E622E4.6010600@indiana.edu
> Thanks Eric
> It's a good thought. I will certainly give it a try.
>
> It still, though, leaves me with two toolchains:
> one 'static' for dataflash and u-boot and a second 'dynamic' for
> kernel and applications (for space considerations)
>
> I am still curious if one could have just one toolchain that rules them
> all ... :)
I removed the -msoftfloat from the
cpu/arm920t/config.mk and
from
cpu/arm920t/at91rm9200/config.mk
After this I have a single toolchain which allows me to build:
* dataflashboot.bin (for AT91RM9200)
* U-Boot
* Linux
* Root File System
It does not allow me to build at91-bootstrap.
>
> Piotr
>
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:[~2007-03-01 6:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 15:51 [Buildroot] static libgcc_s Piotr Adam Zolnierczuk
2007-02-28 18:37 ` Thomas Lundquist
2007-02-28 21:45 ` Erik Andersen
2007-03-01 0:48 ` Piotr Adam Zolnierczuk
2007-03-01 6:13 ` Ulf Samuelsson [this message]
2007-03-01 14:42 ` Zolnierczuk, Piotr
2007-03-01 15:58 ` Ulf Samuelsson
2007-03-01 16:20 ` Piotr Adam Zolnierczuk
2007-03-01 16:55 ` Ulf Samuelsson
[not found] <mailman.1.1172692802.12481.buildroot@uclibc.org>
2007-02-28 20:41 ` Zolnierczuk, Piotr
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='004901c75bcc$356388c0$8c1d10ac@atmel.com' \
--to=ulf@atmel.com \
--cc=buildroot@busybox.net \
/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