From: Vipin KUMAR <vipin.kumar@st.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot-2010.03 build errors with USE_PRIVATE_LIBGCC=yes option
Date: Thu, 15 Jul 2010 16:41:23 +0530 [thread overview]
Message-ID: <4C3EECDB.7000708@st.com> (raw)
In-Reply-To: <20100715091308.EA3EB160691@gemini.denx.de>
On 7/15/2010 2:43 PM, Wolfgang Denk wrote:
> Dear Vipin KUMAR,
>
Dear Wolfgang,
> In message <4C3ED008.1080207@st.com> you wrote:
>>
>>> ok, so the only way is to select the source file containing the fuction from
>>> libgcc and include at source level into your source u-boot tree.
>>> I did the same but I started from the lib dir of linux kernel
>>
>> Hmmm, I was just avoiding it thinking that maybe someone somewhere would have
>> already done that. May be that patch can also be sent to the community
>
> Feel free to go on - we're looking forward to seeing your patch.
>
The problem why I was looking for this is that the tool-chain I am using only
supports -mhard-float option and this toolchain is specifically meant for armv7
(basically Cortex-A9 with FPU enabled).
Since this option -msoft-float is passed from arch/arm/cpu/config.mk, and it
is common for all arm configurations. Is there a good way to pass -mhard-float..
Regards
Vipin
> Best regards,
>
> Wolfgang Denk
>
next prev parent reply other threads:[~2010-07-15 11:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 7:01 [U-Boot] u-boot-2010.03 build errors with USE_PRIVATE_LIBGCC=yes option Vipin KUMAR
2010-07-15 8:15 ` Fabio Giovagnini
2010-07-15 8:59 ` Vipin KUMAR
2010-07-15 9:04 ` Fabio Giovagnini
2010-07-15 9:08 ` Vipin KUMAR
2010-07-15 9:13 ` Wolfgang Denk
2010-07-15 9:51 ` Fabio Giovagnini
2010-07-15 10:22 ` Wolfgang Denk
2010-07-15 10:28 ` Fabio Giovagnini
2010-07-15 11:11 ` Vipin KUMAR [this message]
2010-07-15 17:57 ` Wolfgang Denk
2010-07-15 18:20 ` Dennis Ruffer
2010-07-15 18:50 ` Wolfgang Denk
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=4C3EECDB.7000708@st.com \
--to=vipin.kumar@st.com \
--cc=u-boot@lists.denx.de \
/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