From: "Zhou, Li" <li.zhou@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gcc: add TUNE_CCARGS for CFLAGS_FOR_TARGET of gcc-cross-canadian
Date: Fri, 4 Mar 2016 17:45:22 +0800 [thread overview]
Message-ID: <56D95932.8000609@windriver.com> (raw)
In-Reply-To: <1456831651.25131.1.camel@linuxfoundation.org>
Hi, Richard:
Could you please give me some information about how to do
"selftests for sstate sigs"? Thank you.
On 03/01/2016 07:27 PM, Richard Purdie wrote:
> On Tue, 2016-03-01 at 15:53 +0800, Zhou, Li wrote:
>> Please refer to Peter Seebach's patch earlier:
>> http://lists.openembedded.org/pipermail/openembedded-core/2016-Januar
>> y/115472.html
>> My patch should be based on that.
>> I think the change is not only for canadian build. Thanks.
>>
>> On 03/01/2016 02:12 PM, Khem Raj wrote:
>>> On Mon, Feb 29, 2016 at 6:22 PM, Li Zhou <li.zhou@windriver.com>
>>> wrote:
>>>> Add TUNE_CCARGS for CFLAGS_FOR_TARGET of gcc-cross-canadian to
>>>> solve
>>>> below errors when compiling gcc-cross-canadian-powerpc64 within a
>>>> debug
>>>> build:
>>>>
>>>> configure:3655: checking for suffix of object files
>>>> configure:3677: powerpc64-wrs-linux-gcc -
>>>> -sysroot=......bitbake_build/
>>>> tmp/sysroots/fsl-t2xxx -isystem=/usr/include --sysroot=....../
>>>> bitbake_build/tmp/sysroots/fsl-t2xxx -c -O0 -fno-omit-frame
>>>> -pointer -g
>>>> -pipe -g -Os conftest.c >&5
>>>> {standard input}: Assembler messages:
>>>> {standard input}:23: Error: register save offset not a multiple
>>>> of 8
>>>> {standard input}:24: Error: register save offset not a multiple
>>>> of 8
>>>>
>>>> Signed-off-by: Li Zhou <li.zhou@windriver.com>
>>>> ---
>>>> meta/recipes-devtools/gcc/gcc-cross-canadian.inc | 2 +-
>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/meta/recipes-devtools/gcc/gcc-cross-canadian.inc
>>>> b/meta/recipes-devtools/gcc/gcc-cross-canadian.inc
>>>> index ec1d281..04ae981 100644
>>>> --- a/meta/recipes-devtools/gcc/gcc-cross-canadian.inc
>>>> +++ b/meta/recipes-devtools/gcc/gcc-cross-canadian.inc
>>>> @@ -51,7 +51,7 @@ do_configure () {
>>>> export CPPFLAGS_FOR_BUILD="${BUILD_CPPFLAGS}"
>>>> export CXXFLAGS_FOR_BUILD="${BUILD_CXXFLAGS}"
>>>> export LDFLAGS_FOR_BUILD="${BUILD_LDFLAGS}"
>>>> - export CFLAGS_FOR_TARGET="${TARGET_CFLAGS}"
>>>> + export CFLAGS_FOR_TARGET="${TARGET_CFLAGS}
>>>> ${TUNE_CCARGS}"
>>> Will this cause canadian builds to become too specific instead of
>>> generic common arch
> I agree with Khem, I think there are potential problems this
> introduces. Did you try running the selftests for sstate sigs with this
> change? I suspect it breaks :(
>
> Cheers,
>
> Richard
--
Best Regards!
Zhou Li
Phone number: 86-10-84778511
prev parent reply other threads:[~2016-03-04 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 2:22 [PATCH] gcc: add TUNE_CCARGS for CFLAGS_FOR_TARGET of gcc-cross-canadian Li Zhou
2016-03-01 6:12 ` Khem Raj
2016-03-01 7:53 ` Zhou, Li
2016-03-01 11:27 ` Richard Purdie
2016-03-04 9:45 ` Zhou, Li [this message]
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=56D95932.8000609@windriver.com \
--to=li.zhou@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox