From: Saul Wold <saul.wold@intel.com>
To: Ilya Yanok <yanok@emcraft.com>
Cc: poky@pokylinux.org
Subject: Re: [PATCH 03/25] gcc: crosssdk unset TARGET_FPU
Date: Thu, 20 Jan 2011 09:35:22 -0800 [thread overview]
Message-ID: <4D38725A.9050300@intel.com> (raw)
In-Reply-To: <4D3799C1.7000108@emcraft.com>
On 01/19/2011 06:11 PM, Ilya Yanok wrote:
> Hi Adrian,
>
> I'm sorry, I was wrong in my previous postings.
> I was confused by the gcc-crosssdk recipe name.
> Now I think your solution is perfectly legal, but I still think that
> comment is misleading:
> it's not powerpc arch that does not sipport --with-float=soft, it's
> x86_64 (in my case)!
>
> I think we should just reset TARGET_FPU from crosssdk.bbclass, what do
> you think about it?
>
Adrian,
Will you please re-publish the patch based on Ilya's feedback or let me
know if you want to go with your orignal patch.
Thanks
Sau!
> Regards, Ilya.
>
> On 18.01.2011 03:59, Adrian Alonso wrote:
>> Hi Ilya,
>>
>> I will also look for the proper solution,
>> However un-setting TARGET_FPU only affects the target machines
>> in meta-xilinx layer bsp, so other Powerpc targets are not been affected
>> with this patch.
>>
>> Regards
>>
>> On Mon, Jan 17, 2011 at 5:55 PM, Ilya Yanok <yanok@emcraft.com
>> <mailto:yanok@emcraft.com>> wrote:
>>
>> Hi Adrian,
>>
>> Adrian Alonso <aalonso@...> writes:
>>
>> >
>> > * Configure fails due that --with-float=soft
>> > flag isn't supportted by powerpc arch
>>
>> That's not true. PowerPC support soft-float (and we actually need
>> this for
>> MPC8308 which has e300c3 core without FPU).
>>
>> For me, configure fails with the same message but that's not
>> because PowerPC
>> lacks support for soft-float but cause gcc-crosssdk recipe passes
>> wrong
>> --target= option to the configure script (for me it's
>> x86_86-pokysdk-linux, I'm
>> building on the x86_64 host).
>>
>> > * Unsetting TARGET_FPU this flag to not try to use
>> > this flag
>>
>> So please do NOT unset TARGET_FPU, some targets really need it.
>> I'm looking
>> forward to see a correct solution for this issue.
>>
>> Regards, Ilya.
>>
>>
>> _______________________________________________
>> poky mailing list
>> poky@yoctoproject.org <mailto:poky@yoctoproject.org>
>> https://lists.yoctoproject.org/listinfo/poky
>>
>>
>>
>>
>> --
>> Saludos
>> Adrian Alonso
>> http://aalonso.wordpress.com
>>
>
>
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
next prev parent reply other threads:[~2011-01-20 17:35 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 20:29 [PATCH 01/25] xilinx-kernel: bbclass to handle linux kernel hw/sw integration Adrian Alonso
2011-01-17 20:29 ` [PATCH 02/25] xilinx-boot: bbclass to handle u-boot " Adrian Alonso
2011-01-17 20:29 ` [PATCH 03/25] gcc: crosssdk unset TARGET_FPU Adrian Alonso
2011-01-17 23:55 ` Ilya Yanok
2011-01-18 0:59 ` Adrian Alonso
2011-01-18 1:45 ` Ilya Yanok
2011-01-20 2:11 ` Ilya Yanok
2011-01-20 17:35 ` Saul Wold [this message]
2011-01-20 17:53 ` Adrian Alonso
2011-01-21 0:43 ` Ilya Yanok
2011-01-21 0:47 ` [PATCH] native,nativesdk,crosssdk: reset TARGET_FPU Ilya Yanok
2011-01-17 20:29 ` [PATCH 04/25] u-boot: update version use xilinx-boot bbclass Adrian Alonso
2011-01-17 20:29 ` [PATCH 05/25] u-boot: disable -Os option not supported by gcc Adrian Alonso
2011-01-20 18:53 ` Darren Hart
2011-01-20 18:55 ` Darren Hart
2011-01-20 21:41 ` Adrian Alonso
2011-01-20 23:05 ` Wolfgang Denk
2011-01-20 23:24 ` Richard Purdie
2011-01-22 14:48 ` Wolfgang Denk
2011-01-23 0:11 ` Richard Purdie
2011-01-25 9:09 ` Wolfgang Denk
2011-01-25 22:49 ` Richard Purdie
2011-01-17 20:29 ` [PATCH 06/25] virtex4: fix machine name in u-boot preferred version Adrian Alonso
2011-01-17 20:29 ` [PATCH 07/25] virtex5: " Adrian Alonso
2011-01-17 20:29 ` [PATCH 08/25] xilinx-boot: add ml405 in default target configuration Adrian Alonso
2011-01-17 20:29 ` [PATCH 09/25] u-boot-xilinx: ml405 uartlite support Adrian Alonso
2011-01-17 20:29 ` [PATCH 10/25] xilinx-boot: split configure function Adrian Alonso
2011-01-17 20:29 ` [PATCH 11/25] xilinx-boot: add do_mk_xparam function Adrian Alonso
2011-01-17 20:29 ` [PATCH 12/25] u-boot-xilinx: ml507 uartlite support Adrian Alonso
2011-01-17 20:29 ` [PATCH 13/25] u-boot-xilinx: remove hardcoded include path Adrian Alonso
2011-01-17 20:29 ` [PATCH 14/25] linux-xilinx: update kernel version 2.6.37 rc4 Adrian Alonso
2011-01-17 20:29 ` [PATCH 15/25] linux-xilinx: remove hardcoded include path Adrian Alonso
2011-01-17 20:29 ` [PATCH 16/25] linux-xilinx: add license files checksum Adrian Alonso
2011-01-17 20:29 ` [PATCH 17/25] device-table: add tty uartlite static dev nodes Adrian Alonso
2011-01-17 20:29 ` [PATCH 18/25] u-boot-xilinx: add license files checksum Adrian Alonso
2011-01-17 20:29 ` [PATCH 19/25] tune-ppc405: append ppc440 in PACKAGE_EXTRA_ARCHS Adrian Alonso
2011-01-17 20:29 ` [PATCH 20/25] tune-ppc440: append ppc405 " Adrian Alonso
2011-01-17 20:29 ` [PATCH 21/25] virtex4: update default serial console Adrian Alonso
2011-01-17 20:29 ` [PATCH 22/25] virtex5: " Adrian Alonso
2011-01-17 20:29 ` [PATCH 23/25] defconfig: virtex4 config for linux 2.6.37.rc4 Adrian Alonso
2011-01-17 20:29 ` [PATCH 24/25] defconfig: virtex5 " Adrian Alonso
2011-01-17 20:29 ` [PATCH 25/25] openssl: powerpc gnueabi toolchain support Adrian Alonso
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=4D38725A.9050300@intel.com \
--to=saul.wold@intel.com \
--cc=poky@pokylinux.org \
--cc=yanok@emcraft.com \
/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.