From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] u-boot.inc: properly specify CC for EXTRA_OEMAKE
Date: Thu, 5 Nov 2015 14:16:38 +0100 [thread overview]
Message-ID: <563B56B6.6070307@pseudoterminal.org> (raw)
In-Reply-To: <CAP9ODKqFTU76yL_DqeNku4G3502R00C4K8qwdEtCp5zk1pmJRw@mail.gmail.com>
So, this is because of the TOOLCHAIN_OPTIONS ?
Also, what about the ${CC} ? Right now it won't work properly with clang
for example.
On 11/05/2015 02:14 PM, Otavio Salvador wrote:
> Hello Radek,
>
> On Wed, Nov 4, 2015 at 2:06 PM, Radek Dostal
> <radek.dostal@streamunlimited.com> wrote:
>> ${TOOLCHAIN_OPTIONS} does not contain some important flags such as
>> "-march=armv7-a -mfloat-abi=hard -mfpu=neon -mtune=cortex-a8". It only
>> specifies sysroot as mentioned in commit 923eb657 "u-boot.inc: update
>> linker arguments to pass --sysroot arg"
>>
>> Fixes bug: u-boot 2014.04 build breaks with error:
>> "fatal error: gnu/stubs-soft.h: No such file or directory"
>> when building with hard float compiler as compiler does not receive
>> flag "-mfloat-abi=hard"
>>
>> Before this patch only gcc compiler could be used due to CC explicitly
>> being set to gcc.
>>
>> Signed-off-by: Radek Dostal <radek.dostal@streamunlimited.com>
>> Acked-by: Carlos Rafael Giani <dv@pseudoterminal.org>
> Nack!
>
> The U-Boot is close to the Linux kernel regarding the use of the
> compiler and does a huge set of handling internally to properly pass
> options depending on the SoC, arch and others.
>
> This build error has been fixed in new U-Boot releases and if the
> board required an old version (and cannot be updated) the fix should
> be done on the recipe and not on the common file as it can change,
> behind the scenes, what is in use for several recipes without notice.
>
next prev parent reply other threads:[~2015-11-05 13:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 16:06 [PATCH] u-boot.inc: properly specify CC for EXTRA_OEMAKE Radek Dostal
2015-11-05 13:14 ` Otavio Salvador
2015-11-05 13:16 ` Carlos Rafael Giani [this message]
2015-11-05 14:22 ` Otavio Salvador
2015-11-05 14:23 ` Carlos Rafael Giani
2015-11-10 13:09 ` Tom Rini
2015-11-11 3:59 ` Khem Raj
2015-11-11 12:37 ` Tom Rini
2015-11-11 16:21 ` Khem Raj
2015-11-05 15:19 ` Radek Dostál
2015-11-05 15:32 ` Burton, Ross
2015-11-05 15:47 ` Otavio Salvador
2015-11-05 16:02 ` Radek Dostál
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=563B56B6.6070307@pseudoterminal.org \
--to=dv@pseudoterminal.org \
--cc=openembedded-core@lists.openembedded.org \
/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.