From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Building ARM with Soft-float
Date: Fri, 28 Sep 2007 23:23:45 +0200 [thread overview]
Message-ID: <20070928212345.GB20951@aon.at> (raw)
In-Reply-To: <1191013693.5322.252.camel@elrond.atmel.sweden>
On Fri, Sep 28, 2007 at 11:08:13PM +0200, Ulf Samuelsson wrote:
>fre 2007-09-28 klockan 19:01 +0200 skrev Bernhard Fischer:
>> On Fri, Sep 28, 2007 at 06:28:08PM +0200, Ulf Samuelsson wrote:
>> >fre 2007-09-28 klockan 10:56 +0200 skrev Ulf Samuelsson:
>> >> Tried the Integrator-926ejs default.
>> >> => This works:
>> >>
>> >
>> >Beeing trying the ARM integrator softfloat the whole day.
>> >oabi, instead of eabi, generates a new problem
>> >which was not present a week ago.
>> >The C compiler seems to be built with EABI...
>> >BR2_GNU_TARGET_SUFFIX="uclibc-linux-gnueabi"
>You mean the gcc look at its invocation name to determine
>what it should do.
No notion of the invocation name there.
http://gcc.gnu.org/install/
>Seems stupid to me.
Well, it isn't :P
If you disagree, http://gcc.gnu.org/bugs.html
>What happens if you just call it arm-linux-gcc or even gcc?
You can call it however you like. The drivers follow a somewhat stricter
layout but are hidden from users anyway.
>
>BTW; there are a lot of warning messages about
>calling the tools
I don't understand this.
><arch>-linux-uclibc-<tool>.
>
>Should they not be called <arch>-uclibc-linux-<tool>?
I don't think so. Look at your staging_dir/usr/bin/*
next prev parent reply other threads:[~2007-09-28 21:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 8:56 [Buildroot] Building ARM with Soft-float Ulf Samuelsson
2007-09-28 16:28 ` Ulf Samuelsson
2007-09-28 17:01 ` Bernhard Fischer
2007-09-28 21:08 ` Ulf Samuelsson
2007-09-28 21:23 ` Bernhard Fischer [this message]
2007-09-28 23:24 ` [Buildroot] Buildroot filesystem files' ownership Leonid
2007-09-29 10:12 ` Bernhard Fischer
2007-09-28 16:29 ` [Buildroot] Building ARM with Soft-float Bernhard Fischer
2007-09-28 18:56 ` 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=20070928212345.GB20951@aon.at \
--to=rep.dot.nop@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.