From: Andrew Wiley <debio264@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Can't Login to New System
Date: Mon, 12 Jan 2009 16:22:52 -0600 [thread overview]
Message-ID: <ecbbfeda0901121422v44252c68r61ad8a937557569@mail.gmail.com> (raw)
In-Reply-To: <ecbbfeda0901121422t5aad880amf988d2d55d237dcc@mail.gmail.com>
On Wed, Jan 7, 2009 at 2:23 AM, Bernhard Weirich
<bernhard.weirich@riedel.net> wrote:
> Hi Andrew,
>
> just a wild guess, but I had the same problem and the issue was that neither
> uclib nor kernel was built with floating point support.
> so maybe check if you have floats...
>
> Regards Bernhard
>
This may be a stupid question, but is that setting somewhere in the
buildroot toolchain config, in the kernel config, or somewhere else
entirely? I've looked for it, but I can't seem to find it.
I'm pretty sure the Cirrus Labs cross toolchain uses software floating
point, because in the guide for setting it up, you have to run this
command:
$ sudo mkdir -p /opt/buildroot/toolchain_build_arm_nofpu/ccache-2.4/cache
I thought that was pretty funny when I noticed it. I may be
misinterpretting that, because I'm pretty sure the EDB9302 does have a
FPU, but it may be something wierd about the Qwerk, or I may just be
an idiot. That instruction is found at
http://terk.svn.sourceforge.net/viewvc/terk/embed/trunk/share/docs/QwerkDevelopmentGuide.html#SettingUpTheARMCompiler
Andrew Wiley
next parent reply other threads:[~2009-01-12 22:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1231316636.6374.5.camel@hactar.vie.riedel.net>
[not found] ` <ecbbfeda0901121422t5aad880amf988d2d55d237dcc@mail.gmail.com>
2009-01-12 22:22 ` Andrew Wiley [this message]
2008-12-30 23:20 [Buildroot] Can't Login to New System Andrew Wiley
2008-12-31 0:04 ` Jeremy Kerr
2008-12-31 7:26 ` Peter Korsgaard
[not found] ` <ecbbfeda0812311103q219eea7evdb366ae3cfa8ae4e@mail.gmail.com>
2008-12-31 19:11 ` Andrew Wiley
2009-01-03 19:19 ` Andrew Wiley
2009-01-03 19:53 ` Peter Korsgaard
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=ecbbfeda0901121422v44252c68r61ad8a937557569@mail.gmail.com \
--to=debio264@gmail.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