Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "David Nyström" <david.c.nystrom@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Revert "cross-canadian: Handle powerpc linux verses linux-gnuspe"
Date: Mon, 13 Jan 2014 13:37:15 +0100	[thread overview]
Message-ID: <52D3DDFB.8080803@gmail.com> (raw)
In-Reply-To: <1389366908.19102.223.camel@ted>

On fre 10 jan 2014 16:15:08, Richard Purdie wrote:
> On Fri, 2014-01-10 at 15:48 +0100, David Nyström wrote:
>> The reverted commit seems to introduce some problems for the toolchain tarball
>> for powerpc.
>> I see this both in master and on dora.
>>
>> 1. Looks like the relocation scripts fails for environments:
>>
>> ~/tests/poky [master]
>> $ cat /opt/oel/2014-01-01/environment-setup-ppce500v2-oel-linux | grep "#"
>> export SDKTARGETSYSROOT=##SDKTARGETSYSROOT##
>>
>> ~/tests/poky [master]
>> $ cat /opt/oel/2014-01-01/environment-setup-ppce500v2-oel-linux-gnuspe | grep "#"
>>
>> 2. nativeSDK gnuspe compiler does not allow -mabi=spe
>> ABIEXTENSION is zeroed both for linux-gnuspe and linux
>>
>> 3. Compiler can't create executables.
>> I think this is due to libgcc_s.so from the SDK target sysroot is in mabi=spe.
>>
>> 4. -mspe is included in CC var for both linux and gnuspe.
>> cat /opt/oel/2014-01-01/environment-setup-ppce500v2-oel-linux | grep mabi
>> export CC="powerpc-oel-linux-gcc  -m32 -mcpu=8548 -mabi=spe -mspe ....
>> export CXX="powerpc-oel-linux-g++  -m32 -mcpu=8548 -mabi=spe -mspe ....
>> export CPP="powerpc-oel-linux-gcc -E  -m32 -mcpu=8548 -mabi=spe -mspe ....
>>
>> With the commit reverted, I can successfully build target code with the canadian compiler
>> from the SDK tarball. Only the gnuspe environment file is generated.
>
> Ok, so how do you propose we fix the issues the patch was added to
> address?
>
> Cheers,
>
> Richard
>

Just to clarify bug 5354:
If I understand the bug correctly, this would arise when first building 
the nativesdk tarball on a MACHINE with ABI linux,
and then building the nativesdk for another MACHINE(with the same the 
same TUNE) after altering ABIEXTENSION to linux-gnuspe ?

If I understand bug 5354 correctly, perhaps the tmp/sdk/tarball.here 
can be ABI specific ?
i.e. a generic rule that all nativesdk builds are invalidated if the 
ABI changes. I guess that would mean:
cross-canadian.bbclass: TARGET_ARCH[vardeps] += "ABIEXTENSION"
+ Adding ABIEXTENSION to the nativesdk tarball name.

PPC '=mabi=spe' seems to be one-way compatible,  I could not get the 
non-SPE configured compiler
to work with the SPE sysroot.
Another possible solution would be to always configure the compiler to 
SPE, and use compile time flags in the
environment file to do the selects. + symlinks for the compiler paths.
However, even if we fix it this way for powerpc, we will still have 
this issue with thumb f.ex.

It would be good if the Freescale folks could chime in here.

Br,
David



  reply	other threads:[~2014-01-13 12:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 14:48 [PATCH] Revert "cross-canadian: Handle powerpc linux verses linux-gnuspe" David Nyström
2014-01-10 15:15 ` Richard Purdie
2014-01-13 12:37   ` David Nyström [this message]
2014-01-13 12:41     ` Richard Purdie
2014-01-14 13:23       ` David Nyström
2014-01-17 14:43         ` alexandru.sardan
2014-01-18 11:20           ` Richard Purdie
2014-01-21 17:39             ` alexandru.sardan
2014-01-21 17:43               ` Richard Purdie
2014-01-23 18:22                 ` alexandru.sardan
2014-01-24 15:37                   ` Richard Purdie
2014-01-24 20:56                   ` Phil Blundell
2014-01-28 14:03                     ` alexandru.sardan
2014-01-29 11:38                     ` Richard Purdie
2014-01-31 17:53                       ` alexandru.sardan
2014-01-31 18:07                         ` Richard Purdie
2014-01-31 18:17                           ` alexandru.sardan
2014-02-11 10:07                             ` David Nyström
2014-02-26 18:29                               ` alexandru.sardan
2014-02-26 22:37                                 ` David Nyström
2014-02-27 12:21                                   ` alexandru.sardan
2014-01-21 17:59             ` Khem Raj

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=52D3DDFB.8080803@gmail.com \
    --to=david.c.nystrom@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --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