From: James Newell <jnewell@wgate.com>
To: buildroot@busybox.net
Subject: [Buildroot] building ARM toolchain with nofpu
Date: Thu, 08 Feb 2007 09:26:05 -0500 [thread overview]
Message-ID: <1170944765.10007.16.camel@ndragon.eng.wgate.com> (raw)
In-Reply-To: <168013e20702072350j59e08339maf8cbc711f00d958@mail.gmail.com>
On Thu, 2007-02-08 at 15:50 +0800, carl zhu wrote:
> Hi Yann, so you mean if use this patch, GCC 4.0.4 can work with
> uclibc? I still feel a little strange, because I have googled several
> days before, and I have found someone fixed this issue with applied
> IIRC, Does it do help for this issue?
I think I'm just confused in general.
At first thought I needed a gcc EABI toolchain
(http://wiki.debian.org/ArmEabiPort) for performance reasons but looking
at this table for ARM cores
(http://en.wikipedia.org/wiki/ARM_architecture), I am using the Davinci
which is a ARM926EJ-S, and doesn't appear to have vfp support. I assume
then it would be better to use soft toolchain. Is there any way
distinguish an arm elf binary that was built with vfp, fpa, and soft
using the 'file' command or readelf command? I appreciate the
discussion. I'm fairly new to arm, and buildroot, but enjoying the
learning curve.
Thanks,
Jim
>
> I am new for build cross-compiler.
>
> related link:http://tech.groups.yahoo.com/group/gnuarm/message/1325
>
>
> On 2/8/07, Yann E. MORIN <yann.morin.1998@anciens.enib.fr> wrote:
> On Wednesday 07 February 2007 212, Yann E. MORIN wrote:
> > Short answer: it does not work.
> > See: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29329 [1]
> > (not directly related, but yet, useless on ARM).
>
> I realise I'm being vague. Some explanations below.
>
> In fact, the patch I posted allows one to successfully build a
> x-compiler
> for soft-float armeb (mine is armeb-xscale-linux-uclibc, tuned
> for Xscale).
> Unfortunately, the resulting gcc barfs on the squashfs code in
> the kernel.
> A smaller test-case is available in the bug report, suggesting
> this is quite
> easy to hit.
>
> That's why I've reverted to gcc-4.0.4, which still needs the
> attached patch,
> but Just Work (TM).
>
> Regards,
> Yann E. MORIN.
>
> --
> .-----------------.--------------------.------------------.--------------------.
> | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON |
> Erics' conspiracy: |
> | +0/33 662376056 | Software Designer | \ / CAMPAIGN |
> ^ |
> | --==< ?_? >==--
> ?------------.-------: X AGAINST | /e\ There is no |
> | http://ymorin.is-a-geek.org/ | (*_*) | / \ HTML
> MAIL | """ conspiracy. |
> ?------------------------------?-------?------------------?--------------------?
>
>
next prev parent reply other threads:[~2007-02-08 14:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 0:09 [Buildroot] building ARM toolchain with nofpu Michel Benoit
2007-02-01 19:15 ` Yann E. MORIN
2007-02-01 20:51 ` Michel Benoit
2007-02-01 22:46 ` Ulf Samuelsson
2007-02-05 9:26 ` Michel Benoit
2007-02-07 20:09 ` James Newell
2007-02-07 20:24 ` Yann E. MORIN
2007-02-07 20:36 ` Yann E. MORIN
2007-02-08 7:50 ` carl zhu
2007-02-08 14:26 ` James Newell [this message]
2007-02-09 1:41 ` James Newell
2007-02-09 13:10 ` Bernhard Fischer
2007-03-01 10:01 ` carl zhu
2007-02-08 17:25 ` Bernhard Fischer
2007-02-08 17:33 ` Yann E. MORIN
2007-02-08 17:40 ` Bernhard Fischer
-- strict thread matches above, loose matches on Subject: below --
2007-02-09 14:10 James Newell
2007-02-09 14:29 ` Bernhard Fischer
2007-02-09 17:57 ` Yann E. MORIN
2007-02-09 18:21 ` Bernhard Fischer
2007-02-09 18:48 ` Yann E. MORIN
2007-02-09 14:51 James Newell
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=1170944765.10007.16.camel@ndragon.eng.wgate.com \
--to=jnewell@wgate.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