On Wed, Nov 11, 2015 at 4:37 AM, Tom Rini wrote:
> On Tue, Nov 10, 2015 at 07:59:03PM -0800, Khem Raj wrote:
>>
>> > On Nov 10, 2015, at 5:09 AM, Tom Rini wrote:
>> >
>> > On Thu, Nov 05, 2015 at 03:23:48PM +0100, Carlos Rafael Giani wrote:
>> >> On
On Tue, Nov 10, 2015 at 07:59:03PM -0800, Khem Raj wrote:
>
> > On Nov 10, 2015, at 5:09 AM, Tom Rini wrote:
> >
> > On Thu, Nov 05, 2015 at 03:23:48PM +0100, Carlos Rafael Giani wrote:
> >> On 11/05/2015 03:22 PM, Otavio Salvador wrote:
> >>> Hello Carlos,
> >>>
> >>> On
On Thu, Nov 05, 2015 at 03:23:48PM +0100, Carlos Rafael Giani wrote:
> On 11/05/2015 03:22 PM, Otavio Salvador wrote:
> >Hello Carlos,
> >
> >On Thu, Nov 5, 2015 at 11:16 AM, Carlos Rafael Giani
> > wrote:
> >>So, this is because of the TOOLCHAIN_OPTIONS ?
> >>Also, what
> On Nov 10, 2015, at 5:09 AM, Tom Rini wrote:
>
> On Thu, Nov 05, 2015 at 03:23:48PM +0100, Carlos Rafael Giani wrote:
>> On 11/05/2015 03:22 PM, Otavio Salvador wrote:
>>> Hello Carlos,
>>>
>>> On Thu, Nov 5, 2015 at 11:16 AM, Carlos Rafael Giani
>>>
Hello Carlos,
On Thu, Nov 5, 2015 at 11:16 AM, Carlos Rafael Giani
wrote:
> So, this is because of the TOOLCHAIN_OPTIONS ?
> Also, what about the ${CC} ? Right now it won't work properly with clang for
> example.
The clang is problem might involve us to rework something
On 11/05/2015 03:22 PM, Otavio Salvador wrote:
Hello Carlos,
On Thu, Nov 5, 2015 at 11:16 AM, Carlos Rafael Giani
wrote:
So, this is because of the TOOLCHAIN_OPTIONS ?
Also, what about the ${CC} ? Right now it won't work properly with clang for
example.
The clang is
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
wrote:
Hello Radek,
On Wed, Nov 4, 2015 at 2:06 PM, Radek Dostal
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
On 11/05/2015 04:47 PM, Otavio Salvador wrote:
I don't know; I strongly advise the upgrade for the board if you have
the resources (schematic, time, ...) otherwise a recipe workaround is
the best alternative.
Thank you, update of the u-boot is planned for early 2016, till that
time we have to
On 5 November 2015 at 15:19, Radek Dostál
wrote:
> Thanks a lot for your valuable input. I was not aware of the fact that it
> was fixed in the upstream already. If you know the commit out of your head,
> it would be great if you could share it.
>
For what it's
On Thu, Nov 5, 2015 at 1:19 PM, Radek Dostál
wrote:
>> 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,
Hi Otavio,
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
${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
13 matches
Mail list logo