From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] AVR32 4.1.2 toolchain build issues[was svncommit:trunk/buildroot: target/devicetarget/device/Atmel targetetc...]
Date: Tue, 16 Oct 2007 07:57:42 +0200 [thread overview]
Message-ID: <006a01c80fb9$f07c8d40$01c4af0a@Glamdring> (raw)
In-Reply-To: 1192511723.28237.2.camel@localhost.localdomain
> On Tue, 2007-10-16 at 02:46 +0100, Thiago A. Corr?a wrote:
>> Ok.... got it to build... it happens to be that atngw100_defconfig now
>> builds to a dir without nofp sufix, which makes me wonder if ppl have
>> decided weather this thing has or doesn't has an FP, perhaps it's a
>> paradox, or a dogma. You just have to belive it works. *smile*
>>
>
> It does not have an FPU, probably just a bad defconfig.
>
Why not add a "depends on !AVR32" patch to uClibc KConfig which disables
the possibility to select the bad FPU option?
If an AVR32 with a FPU appears (wish, wish :-) then this option can be
removed.
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2007-10-16 5:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 14:20 [Buildroot] AVR32 4.1.2 toolchain build issues [was svn commit: trunk/buildroot: target/device target/device/Atmel target etc...] Thiago A. Corrêa
2007-10-15 21:25 ` [Buildroot] AVR32 4.1.2 toolchain build issues [was svn commit:trunk/buildroot: " Ulf Samuelsson
2007-10-15 22:17 ` don
2007-10-15 22:22 ` [Buildroot] AVR32 4.1.2 toolchain build issues [was svncommit:trunk/buildroot: target/device target/device/Atmel targetetc...] Ulf Samuelsson
2007-10-15 23:49 ` don
2007-10-16 1:46 ` Thiago A. Corrêa
2007-10-16 5:15 ` Hans-Christian Egtvedt
2007-10-16 5:57 ` Ulf Samuelsson [this message]
2007-10-16 11:32 ` Thiago A. Corrêa
2007-10-16 11:46 ` Hans-Christian Egtvedt
2007-10-16 13:10 ` Thomas Lundquist
2007-10-16 5:36 ` Ulf Samuelsson
2007-10-16 5:27 ` [Buildroot] AVR32 4.1.2 toolchain build issues [wassvncommit:trunk/buildroot: target/device target/device/Atmeltargetetc...] Ulf Samuelsson
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='006a01c80fb9$f07c8d40$01c4af0a@Glamdring' \
--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