GCC 4.9 and Morty

GCC 4.9 and Morty

[Lee, Yong]

[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]

I have a bunch of apps that require an old version of GCC (4.9 or less).
There are a few versions of GCC available in my Morty based SDK.

build@6e35408e8fa5:~/tisdk/build$ bitbake-layers show-recipes gcc
WARNING: No recipes available for:
  /home/build/tisdk/sources/meta-openamp/recipes-bsp/device-tree/device-tree-generation_%.bbappend
Parsing recipes..done.
=== Matching recipes: ===
gcc:
  meta-linaro-toolchain linaro-4.9
  meta-linaro-toolchain linaro-6.2
  meta                 6.2.0
  meta                 5.4.0
  meta-linaro-toolchain linaro-5.3
  meta-linaro-toolchain linaro-5.2

Immediately I have set the PREFERRED_VERSION of gcc to 4.9 but bitbake does not go beyond configuration.

I believe 4.9 + morty combination has not been tested at all. I understand my apps need to get updated, but that's not my call.

Adam
The information in this email and any attachments may contain proprietary and confidential information that is intended for the addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, retention or use of the contents of this information is prohibited. If you have received this email in error, please immediately contact the sender and delete the email.

[-- Attachment #2: Type: text/html, Size: 4480 bytes --]

Re: GCC 4.9 and Morty

[Khem Raj]

On Tue, Oct 24, 2017 at 6:56 AM, Lee, Yong <Yong.Lee@johnsonoutdoors.com> wrote:
> I have a bunch of apps that require an old version of GCC (4.9 or less).
>
> There are a few versions of GCC available in my Morty based SDK.
>
>
>
> build@6e35408e8fa5:~/tisdk/build$ bitbake-layers show-recipes gcc
>
> WARNING: No recipes available for:
>
>
> /home/build/tisdk/sources/meta-openamp/recipes-bsp/device-tree/device-tree-generation_%.bbappend
>
> Parsing recipes..done.
>
> === Matching recipes: ===
>
> gcc:
>
>   meta-linaro-toolchain linaro-4.9
>
>   meta-linaro-toolchain linaro-6.2
>
>   meta                 6.2.0
>
>   meta                 5.4.0
>
>   meta-linaro-toolchain linaro-5.3
>
>   meta-linaro-toolchain linaro-5.2
>
>
>
> Immediately I have set the PREFERRED_VERSION of gcc to 4.9 but bitbake does
> not go beyond configuration.
>
>

Please post the error and change you did to enable 4.9

>
> I believe 4.9 + morty combination has not been tested at all. I understand
> my apps need to get updated, but that’s not my call.

OE-core and yocto releases by default do not test toolchains coming
from other layers
so essentially 6.2 is whats the default compiler with morty and thats
what is most tested
however, others might have tested the other combinations with morty,

Re: GCC 4.9 and Morty

[Lee, Yong]

[-- Attachment #1: Type: text/plain, Size: 2104 bytes --]

Thanks Raj for the input. Attached the logs. Please take a look.
The .diff file is based on the toolchain-linaro.inc file shipped with TI's SDK [1].

I will try to configure the SDK to use the internal toolchain and see if I can decouple myself from the external toolchain to simplify things.

Adam

[1] http://arago-project.org/git/?p=meta-arago.git;a=blob;f=meta-arago-distro/conf/distro/include/toolchain-linaro.inc;h=20a65174f269c1e1a5984c5476a2ab4e5dfc42b5;hb=refs/heads/morty

-----Original Message-----
From: Khem Raj [mailto:raj.khem@gmail.com] 
Sent: Tuesday, October 24, 2017 12:26 PM
To: Lee, Yong <Yong.Lee@johnsonoutdoors.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] GCC 4.9 and Morty

*EXTERNAL EMAIL*


On Tue, Oct 24, 2017 at 6:56 AM, Lee, Yong <Yong.Lee@johnsonoutdoors.com> wrote:
> I have a bunch of apps that require an old version of GCC (4.9 or less).
>
> There are a few versions of GCC available in my Morty based SDK.
>
>
>
> build@6e35408e8fa5:~/tisdk/build$ bitbake-layers show-recipes gcc
>
> WARNING: No recipes available for:
>
>
> /home/build/tisdk/sources/meta-openamp/recipes-bsp/device-tree/device-
> tree-generation_%.bbappend
>
> Parsing recipes..done.
>
> === Matching recipes: ===
>
> gcc:
>
>   meta-linaro-toolchain linaro-4.9
>
>   meta-linaro-toolchain linaro-6.2
>
>   meta                 6.2.0
>
>   meta                 5.4.0
>
>   meta-linaro-toolchain linaro-5.3
>
>   meta-linaro-toolchain linaro-5.2
>
>
>
> Immediately I have set the PREFERRED_VERSION of gcc to 4.9 but bitbake 
> does not go beyond configuration.
>
>

Please post the error and change you did to enable 4.9

>
> I believe 4.9 + morty combination has not been tested at all. I 
> understand my apps need to get updated, but that’s not my call.

OE-core and yocto releases by default do not test toolchains coming from other layers so essentially 6.2 is whats the default compiler with morty and thats what is most tested however, others might have tested the other combinations with morty,

[-- Attachment #2: bitbake_gcc.error --]
[-- Type: application/octet-stream, Size: 8655 bytes --]



build@6e35408e8fa5:~/tisdk/build$ bitbake gcc
NOTE: Started PRServer with DBfile: /home/build/tisdk/build/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 60820, PID: 39034
Parsing recipes: 100% |#########################################################################################################| Time: 0:00:18
Parsing of 2536 .bb files complete (0 cached, 2536 parsed). 3284 targets, 300 skipped, 0 masked, 0 errors.
WARNING: No recipes available for:
  /home/build/tisdk/sources/meta-openamp/recipes-bsp/device-tree/device-tree-generation_%.bbappend
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION        = "1.32.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-16.04"
TARGET_SYS        = "arm-linux-gnueabi"
MACHINE           = "am57xx-evm"
DISTRO            = "arago"
DISTRO_VERSION    = "2017.10"
TUNE_FEATURES     = "arm armv7a vfp thumb neon       callconvention-hard"
TARGET_FPU        = "hard"
meta-arago-distro
meta-arago-extras = "morty:d590d90a57359640ea546c7638788b0600546384"
meta-browser      = "master:26d50665e2f7223c5f4ad7481a8d2431e7cb55fb"
meta-openamp      = "morty:8a214032bfb7e8124bc1485c70c69f7d60abb819"
meta-qt5          = "morty:2c9f0e4eb0e9097f6f872ec1e1d81768a8ab5f1b"
meta-networking
meta-ruby
meta-python
meta-oe
meta-gnome        = "morty:b40116cf457b88a2db14b86fda9627fb34d56ae6"
meta-ti           = "morty:b0531c2266f8138f91d5fd69f8c86fbf7d0770f1"
meta-linaro-toolchain
meta-optee        = "morty:5d2cb685217794293ea2bab18d7e62019c329d06"
meta              = "morty:c79b479ab4b129007c6679bb0bdd8e2ec7ecb6ad"
Initialising tasks: 100% |######################################################################################################| Time: 0:00:01
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: gcc-linaro-4.9-r2015.06 do_configure: Function failed: do_configure (log file is located at /home/build/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/gcc/linaro-4.9-r2015.06/temp/log.do_configure.39190)
ERROR: Logfile of failure stored in: /home/build/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/gcc/linaro-4.9-r2015.06/temp/log.do_configure.39190
Log data follows:
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'arm-32', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']
| DEBUG: Executing shell function autotools_preconfigure
| DEBUG: Shell function autotools_preconfigure finished
| DEBUG: Executing python function autotools_copy_aclocals
| DEBUG: Considering setscene task: ['pseudo-native', 'do_populate_sysroot']
| DEBUG:   considering dependency: ['libtool-cross', 'do_populate_sysroot']
| DEBUG:   considering dependency: ['pseudo-native', 'do_populate_sysroot']
| NOTE: Skipping setscene dependency virtual:native:/home/build/tisdk/sources/oe-core/meta/recipes-devtools/pseudo/pseudo_1.8.1.bb:do_populate_sysroot for m4 macro copying
| DEBUG: Considering setscene task: ['pseudo-native', 'do_populate_sysroot']
| DEBUG:   considering dependency: ['pseudo-native', 'do_populate_sysroot']
| DEBUG:   considering dependency: ['libmpc', 'do_populate_sysroot']
| NOTE: Skipping setscene dependency virtual:native:/home/build/tisdk/sources/oe-core/meta/recipes-devtools/pseudo/pseudo_1.8.1.bb:do_populate_sysroot for m4 macro copying
| DEBUG: Considering setscene task: ['pseudo-native', 'do_populate_sysroot']
| DEBUG:   considering dependency: ['pseudo-native', 'do_populate_sysroot']
| DEBUG:   considering dependency: ['gmp', 'do_populate_sysroot']
| NOTE: Skipping setscene dependency virtual:native:/home/build/tisdk/sources/oe-core/meta/recipes-devtools/pseudo/pseudo_1.8.1.bb:do_populate_sysroot for m4 macro copying
| DEBUG: Considering setscene task: ['pseudo-native', 'do_populate_sysroot']
| DEBUG:   considering dependency: ['pseudo-native', 'do_populate_sysroot']
| DEBUG:   considering dependency: ['mpfr', 'do_populate_sysroot']
| NOTE: Skipping setscene dependency virtual:native:/home/build/tisdk/sources/oe-core/meta/recipes-devtools/pseudo/pseudo_1.8.1.bb:do_populate_sysroot for m4 macro copying
| DEBUG: Considering setscene task: ['texinfo-dummy-native', 'do_populate_sysroot']
| DEBUG:   considering dependency: ['automake-native', 'do_populate_sysroot']
| DEBUG: Considering setscene task: ['pseudo-native', 'do_populate_sysroot']
| DEBUG:   considering dependency: ['zlib', 'do_populate_sysroot']
| DEBUG:   considering dependency: ['pseudo-native', 'do_populate_sysroot']
| NOTE: Skipping setscene dependency virtual:native:/home/build/tisdk/sources/oe-core/meta/recipes-devtools/pseudo/pseudo_1.8.1.bb:do_populate_sysroot for m4 macro copying
| DEBUG: Considering setscene task: ['m4-native', 'do_populate_sysroot']
| DEBUG:   considering dependency: ['m4-native', 'do_populate_sysroot']
| DEBUG:   considering dependency: ['autoconf-native', 'do_populate_sysroot']
| DEBUG: Considering setscene task: ['pseudo-native', 'do_populate_sysroot']
| DEBUG:   considering dependency: ['pseudo-native', 'do_populate_sysroot']
| DEBUG:   considering dependency: ['external-linaro-toolchain', 'do_populate_sysroot']
| NOTE: Skipping setscene dependency virtual:native:/home/build/tisdk/sources/oe-core/meta/recipes-devtools/pseudo/pseudo_1.8.1.bb:do_populate_sysroot for m4 macro copying
| DEBUG: Considering setscene task: ['linux-libc-headers', 'do_populate_sysroot']
| DEBUG:   considering dependency: ['external-linaro-toolchain', 'do_populate_sysroot']
| DEBUG: Considering setscene task: ['external-linaro-toolchain-cross-arm', 'do_populate_sysroot']
| DEBUG:   considering dependency: ['external-linaro-toolchain', 'do_populate_sysroot']
| DEBUG:   considering dependency: ['external-linaro-toolchain-cross-arm', 'do_populate_sysroot']
| NOTE: Skipping setscene dependency /home/build/tisdk/sources/meta-arago/meta-arago-extras/recipes-core/meta/external-linaro-toolchain-cross.bb:do_populate_sysroot for m4 macro copying
| DEBUG: Considering setscene task: ['pseudo-native', 'do_populate_sysroot']
| DEBUG:   considering dependency: ['pseudo-native', 'do_populate_sysroot']
| DEBUG:   considering dependency: ['linux-libc-headers', 'do_populate_sysroot']
| NOTE: Skipping setscene dependency virtual:native:/home/build/tisdk/sources/oe-core/meta/recipes-devtools/pseudo/pseudo_1.8.1.bb:do_populate_sysroot for m4 macro copying
| DEBUG: Considering setscene task: ['unifdef-native', 'do_populate_sysroot']
| DEBUG:   considering dependency: ['linux-libc-headers', 'do_populate_sysroot']
| DEBUG:   considering dependency: ['unifdef-native', 'do_populate_sysroot']
| NOTE: Skipping setscene dependency virtual:native:/home/build/tisdk/sources/oe-core/meta/recipes-devtools/unifdef/unifdef_2.11.bb:do_populate_sysroot for m4 macro copying
| DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'arm-32', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']
| DEBUG: Python function autotools_copy_aclocals finished
| DEBUG: Executing python function gcc_multilib_setup
| DEBUG: Python function gcc_multilib_setup finished
| DEBUG: Executing shell function do_configure
| sed: can't read /home/build/tisdk/build/arago-tmp-external-linaro-toolchain/work-shared/gcc-linaro-4.9-r2015.06/gcc-linaro-4.9-2015.06/libcc1/configure: No such file or directory
| WARNING: /home/build/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/gcc/linaro-4.9-r2015.06/temp/run.do_configure.39190:1 exit 2 from 'sed -i -e 's/hardcode_into_libs=yes/hardcode_into_libs=no/' /home/build/tisdk/build/arago-tmp-external-linaro-toolchain/work-shared/gcc-linaro-4.9-r2015.06/gcc-linaro-4.9-2015.06/libcc1/configure'
| ERROR: Function failed: do_configure (log file is located at /home/build/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/gcc/linaro-4.9-r2015.06/temp/log.do_configure.39190)
ERROR: Task (/home/build/tisdk/sources/meta-linaro/meta-linaro-toolchain/recipes-devtools/gcc/gcc_linaro-4.9.bb:do_configure) failed with exit code '1'
NOTE: Tasks Summary: Attempted 430 tasks of which 429 didn't need to be rerun and 1 failed.
NOTE: Writing buildhistory

Summary: 1 task failed:
  /home/build/tisdk/sources/meta-linaro/meta-linaro-toolchain/recipes-devtools/gcc/gcc_linaro-4.9.bb:do_configure
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.


[-- Attachment #3: gcc.diff --]
[-- Type: application/octet-stream, Size: 1152 bytes --]


build@6e35408e8fa5:~/tisdk/sources/meta-arago/meta-arago-distro/conf/distro/include$ git diff .
diff --git a/meta-arago-distro/conf/distro/include/toolchain-linaro.inc b/meta-arago-distro/conf/distro/include/toolchain-linaro.inc
index 20a6517..6e89ea6 100644
--- a/meta-arago-distro/conf/distro/include/toolchain-linaro.inc
+++ b/meta-arago-distro/conf/distro/include/toolchain-linaro.inc
@@ -31,7 +31,8 @@ PREFERRED_PROVIDER_libgcc = "external-linaro-toolchain"
 PREFERRED_PROVIDER_gcc-runtime = "external-linaro-toolchain"

 # Set Cross and SDK toolchain preferences
-SDKGCCVERSION ?= "linaro-6.2%"
+#SDKGCCVERSION ?= "linaro-6.2%"
+SDKGCCVERSION ?= "linar-4.9%"
 SDKBINUVERSION ?= "linaro-2.27%"
 SDKGLIBCVERSION ?= "2.24%"
 SDKLINUXLIBCVERSION ?= "4.9%"
@@ -49,7 +50,8 @@ PREFERRED_VERSION_nativesdk-glibc-initial ?= "${SDKGLIBCVERSION}"

 # Set target toolchain preferences to match Cross/SDK by default
 # Can be overwritten globally, if needed
-GCCVERSION ?= "linaro-6.2%"
+# GCCVERSION ?= "linaro-6.2%"
+GCCVERSION ?= "linaro-4.9%"
 BINUVERSION ?= "linaro-2.27%"
 GLIBCVERSION ?= "2.24%"
 GLIBCINITVERSION ?= "2.24%"

Re: GCC 4.9 and Morty

[Khem Raj]

On Tue, Oct 24, 2017 at 10:33 AM, Lee, Yong
<Yong.Lee@johnsonoutdoors.com> wrote:
> Thanks Raj for the input. Attached the logs. Please take a look.
> The .diff file is based on the toolchain-linaro.inc file shipped with TI's SDK [1].
>

Your changes look fine.

> I will try to configure the SDK to use the internal toolchain and see if I can decouple myself from the external toolchain to simplify things.
>

you might have to bug your SDK provider for gcc 4.9 build issue


> Adam
>
> [1] http://arago-project.org/git/?p=meta-arago.git;a=blob;f=meta-arago-distro/conf/distro/include/toolchain-linaro.inc;h=20a65174f269c1e1a5984c5476a2ab4e5dfc42b5;hb=refs/heads/morty
>
> -----Original Message-----
> From: Khem Raj [mailto:raj.khem@gmail.com]
> Sent: Tuesday, October 24, 2017 12:26 PM
> To: Lee, Yong <Yong.Lee@johnsonoutdoors.com>
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] GCC 4.9 and Morty
>
> *EXTERNAL EMAIL*
>
>
> On Tue, Oct 24, 2017 at 6:56 AM, Lee, Yong <Yong.Lee@johnsonoutdoors.com> wrote:
>> I have a bunch of apps that require an old version of GCC (4.9 or less).
>>
>> There are a few versions of GCC available in my Morty based SDK.
>>
>>
>>
>> build@6e35408e8fa5:~/tisdk/build$ bitbake-layers show-recipes gcc
>>
>> WARNING: No recipes available for:
>>
>>
>> /home/build/tisdk/sources/meta-openamp/recipes-bsp/device-tree/device-
>> tree-generation_%.bbappend
>>
>> Parsing recipes..done.
>>
>> === Matching recipes: ===
>>
>> gcc:
>>
>>   meta-linaro-toolchain linaro-4.9
>>
>>   meta-linaro-toolchain linaro-6.2
>>
>>   meta                 6.2.0
>>
>>   meta                 5.4.0
>>
>>   meta-linaro-toolchain linaro-5.3
>>
>>   meta-linaro-toolchain linaro-5.2
>>
>>
>>
>> Immediately I have set the PREFERRED_VERSION of gcc to 4.9 but bitbake
>> does not go beyond configuration.
>>
>>
>
> Please post the error and change you did to enable 4.9
>
>>
>> I believe 4.9 + morty combination has not been tested at all. I
>> understand my apps need to get updated, but that’s not my call.
>
> OE-core and yocto releases by default do not test toolchains coming from other layers so essentially 6.2 is whats the default compiler with morty and thats what is most tested however, others might have tested the other combinations with morty,

Re: GCC 4.9 and Morty

[Lee, Yong]

Thank you.
I switched to internal toolchain and building GCC 5.4 (included in meta) is complete and is onto glibc.

In summary, TI SDK appears to be broken as the none-default GCC version included in their package (ie. Linaro 4.9 and Linaro 5.2) fails to build.

Adam

-----Original Message-----
From: Khem Raj [mailto:raj.khem@gmail.com] 
Sent: Tuesday, October 24, 2017 1:46 PM
To: Lee, Yong <Yong.Lee@johnsonoutdoors.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] GCC 4.9 and Morty

On Tue, Oct 24, 2017 at 10:33 AM, Lee, Yong <Yong.Lee@johnsonoutdoors.com> wrote:
> Thanks Raj for the input. Attached the logs. Please take a look.
> The .diff file is based on the toolchain-linaro.inc file shipped with TI's SDK [1].
>

Your changes look fine.

> I will try to configure the SDK to use the internal toolchain and see if I can decouple myself from the external toolchain to simplify things.
>

you might have to bug your SDK provider for gcc 4.9 build issue


> Adam
>
> [1] 
> http://arago-project.org/git/?p=meta-arago.git;a=blob;f=meta-arago-dis
> tro/conf/distro/include/toolchain-linaro.inc;h=20a65174f269c1e1a5984c5
> 476a2ab4e5dfc42b5;hb=refs/heads/morty
>
> -----Original Message-----
> From: Khem Raj [mailto:raj.khem@gmail.com]
> Sent: Tuesday, October 24, 2017 12:26 PM
> To: Lee, Yong <Yong.Lee@johnsonoutdoors.com>
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] GCC 4.9 and Morty
>
> *EXTERNAL EMAIL*
>
>
> On Tue, Oct 24, 2017 at 6:56 AM, Lee, Yong <Yong.Lee@johnsonoutdoors.com> wrote:
>> I have a bunch of apps that require an old version of GCC (4.9 or less).
>>
>> There are a few versions of GCC available in my Morty based SDK.
>>
>>
>>
>> build@6e35408e8fa5:~/tisdk/build$ bitbake-layers show-recipes gcc
>>
>> WARNING: No recipes available for:
>>
>>
>> /home/build/tisdk/sources/meta-openamp/recipes-bsp/device-tree/device
>> -
>> tree-generation_%.bbappend
>>
>> Parsing recipes..done.
>>
>> === Matching recipes: ===
>>
>> gcc:
>>
>>   meta-linaro-toolchain linaro-4.9
>>
>>   meta-linaro-toolchain linaro-6.2
>>
>>   meta                 6.2.0
>>
>>   meta                 5.4.0
>>
>>   meta-linaro-toolchain linaro-5.3
>>
>>   meta-linaro-toolchain linaro-5.2
>>
>>
>>
>> Immediately I have set the PREFERRED_VERSION of gcc to 4.9 but 
>> bitbake does not go beyond configuration.
>>
>>
>
> Please post the error and change you did to enable 4.9
>
>>
>> I believe 4.9 + morty combination has not been tested at all. I 
>> understand my apps need to get updated, but that’s not my call.
>
> OE-core and yocto releases by default do not test toolchains coming 
> from other layers so essentially 6.2 is whats the default compiler 
> with morty and thats what is most tested however, others might have 
> tested the other combinations with morty,

Re: GCC 4.9 and Morty

[Denys Dmytriyenko]

On Tue, Oct 24, 2017 at 06:37:17PM +0000, Lee, Yong wrote:
> Thank you.
> I switched to internal toolchain and building GCC 5.4 (included in meta) is 
> complete and is onto glibc.
> 
> In summary, TI SDK appears to be broken as the none-default GCC version 
> included in their package (ie. Linaro 4.9 and Linaro 5.2) fails to build.

There's nothing wrong with TI SDK - the issue is often with the Linaro 
prebuilt toolchain changing little things from version to version and breaking 
corresponding recipes. Unfortunately, external toolchain is required, hence I 
only support 1 specific Linaro toolchain version per release - 7.x in rocko, 
6.x in morty, 5.x in krogoth, 4.9 in fido, etc. So, if you need a different 
Linaro toolchain version, either switch to a corresponding release setup, or 
try porting those recipes.
Alternatively, you can always switch to internal toolchain by simply passing 
TOOLCHAIN_TYPE=internal to TI SDK build. It's not the default and doesn't get 
tested very much against TI SDK, but I try to ensure nothing is broken in each 
relesae. Though, gcc7 is still work in progress.

-- 
Denys


> -----Original Message-----
> From: Khem Raj [mailto:raj.khem@gmail.com] 
> Sent: Tuesday, October 24, 2017 1:46 PM
> To: Lee, Yong <Yong.Lee@johnsonoutdoors.com>
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] GCC 4.9 and Morty
> 
> On Tue, Oct 24, 2017 at 10:33 AM, Lee, Yong <Yong.Lee@johnsonoutdoors.com> wrote:
> > Thanks Raj for the input. Attached the logs. Please take a look.
> > The .diff file is based on the toolchain-linaro.inc file shipped with TI's SDK [1].
> >
> 
> Your changes look fine.
> 
> > I will try to configure the SDK to use the internal toolchain and see if I can decouple myself from the external toolchain to simplify things.
> >
> 
> you might have to bug your SDK provider for gcc 4.9 build issue
> 
> 
> > Adam
> >
> > [1] 
> > http://arago-project.org/git/?p=meta-arago.git;a=blob;f=meta-arago-dis
> > tro/conf/distro/include/toolchain-linaro.inc;h=20a65174f269c1e1a5984c5
> > 476a2ab4e5dfc42b5;hb=refs/heads/morty
> >
> > -----Original Message-----
> > From: Khem Raj [mailto:raj.khem@gmail.com]
> > Sent: Tuesday, October 24, 2017 12:26 PM
> > To: Lee, Yong <Yong.Lee@johnsonoutdoors.com>
> > Cc: openembedded-core@lists.openembedded.org
> > Subject: Re: [OE-core] GCC 4.9 and Morty
> >
> > *EXTERNAL EMAIL*
> >
> >
> > On Tue, Oct 24, 2017 at 6:56 AM, Lee, Yong <Yong.Lee@johnsonoutdoors.com> wrote:
> >> I have a bunch of apps that require an old version of GCC (4.9 or less).
> >>
> >> There are a few versions of GCC available in my Morty based SDK.
> >>
> >>
> >>
> >> build@6e35408e8fa5:~/tisdk/build$ bitbake-layers show-recipes gcc
> >>
> >> WARNING: No recipes available for:
> >>
> >>
> >> /home/build/tisdk/sources/meta-openamp/recipes-bsp/device-tree/device
> >> -
> >> tree-generation_%.bbappend
> >>
> >> Parsing recipes..done.
> >>
> >> === Matching recipes: ===
> >>
> >> gcc:
> >>
> >>   meta-linaro-toolchain linaro-4.9
> >>
> >>   meta-linaro-toolchain linaro-6.2
> >>
> >>   meta                 6.2.0
> >>
> >>   meta                 5.4.0
> >>
> >>   meta-linaro-toolchain linaro-5.3
> >>
> >>   meta-linaro-toolchain linaro-5.2
> >>
> >>
> >>
> >> Immediately I have set the PREFERRED_VERSION of gcc to 4.9 but 
> >> bitbake does not go beyond configuration.
> >>
> >>
> >
> > Please post the error and change you did to enable 4.9
> >
> >>
> >> I believe 4.9 + morty combination has not been tested at all. I 
> >> understand my apps need to get updated, but that’s not my call.
> >
> > OE-core and yocto releases by default do not test toolchains coming 
> > from other layers so essentially 6.2 is whats the default compiler 
> > with morty and thats what is most tested however, others might have 
> > tested the other combinations with morty,
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: GCC 4.9 and Morty

[Denys Dmytriyenko]

On Thu, Oct 26, 2017 at 08:25:00AM -0400, Denys Dmytriyenko wrote:
> On Tue, Oct 24, 2017 at 06:37:17PM +0000, Lee, Yong wrote:
> > Thank you.
> > I switched to internal toolchain and building GCC 5.4 (included in meta) is 
> > complete and is onto glibc.
> > 
> > In summary, TI SDK appears to be broken as the none-default GCC version 
> > included in their package (ie. Linaro 4.9 and Linaro 5.2) fails to build.
> 
> There's nothing wrong with TI SDK - the issue is often with the Linaro 
> prebuilt toolchain changing little things from version to version and breaking 
> corresponding recipes. Unfortunately, external toolchain is required, hence I 
> only support 1 specific Linaro toolchain version per release - 7.x in rocko, 
> 6.x in morty, 5.x in krogoth, 4.9 in fido, etc. So, if you need a different 
> Linaro toolchain version, either switch to a corresponding release setup, or 
> try porting those recipes.
> Alternatively, you can always switch to internal toolchain by simply passing 
> TOOLCHAIN_TYPE=internal to TI SDK build. It's not the default and doesn't get 
> tested very much against TI SDK, but I try to ensure nothing is broken in each 
> relesae. Though, gcc7 is still work in progress.

BTW, meta-arago has its own mailing list, as well as meta-linaro has one too. 
Complaining to OE-Core about specifics like this is like posting to LKML about 
issues with your Linux distro... As Khem said - ask your SDK provider. And 
maybe try doing that first - could probably save you a lot of headache...


> > -----Original Message-----
> > From: Khem Raj [mailto:raj.khem@gmail.com] 
> > Sent: Tuesday, October 24, 2017 1:46 PM
> > To: Lee, Yong <Yong.Lee@johnsonoutdoors.com>
> > Cc: openembedded-core@lists.openembedded.org
> > Subject: Re: [OE-core] GCC 4.9 and Morty
> > 
> > On Tue, Oct 24, 2017 at 10:33 AM, Lee, Yong <Yong.Lee@johnsonoutdoors.com> wrote:
> > > Thanks Raj for the input. Attached the logs. Please take a look.
> > > The .diff file is based on the toolchain-linaro.inc file shipped with TI's SDK [1].
> > >
> > 
> > Your changes look fine.
> > 
> > > I will try to configure the SDK to use the internal toolchain and see if I can decouple myself from the external toolchain to simplify things.
> > >
> > 
> > you might have to bug your SDK provider for gcc 4.9 build issue
> > 
> > 
> > > Adam
> > >
> > > [1] 
> > > http://arago-project.org/git/?p=meta-arago.git;a=blob;f=meta-arago-dis
> > > tro/conf/distro/include/toolchain-linaro.inc;h=20a65174f269c1e1a5984c5
> > > 476a2ab4e5dfc42b5;hb=refs/heads/morty
> > >
> > > -----Original Message-----
> > > From: Khem Raj [mailto:raj.khem@gmail.com]
> > > Sent: Tuesday, October 24, 2017 12:26 PM
> > > To: Lee, Yong <Yong.Lee@johnsonoutdoors.com>
> > > Cc: openembedded-core@lists.openembedded.org
> > > Subject: Re: [OE-core] GCC 4.9 and Morty
> > >
> > > *EXTERNAL EMAIL*
> > >
> > >
> > > On Tue, Oct 24, 2017 at 6:56 AM, Lee, Yong <Yong.Lee@johnsonoutdoors.com> wrote:
> > >> I have a bunch of apps that require an old version of GCC (4.9 or less).
> > >>
> > >> There are a few versions of GCC available in my Morty based SDK.
> > >>
> > >>
> > >>
> > >> build@6e35408e8fa5:~/tisdk/build$ bitbake-layers show-recipes gcc
> > >>
> > >> WARNING: No recipes available for:
> > >>
> > >>
> > >> /home/build/tisdk/sources/meta-openamp/recipes-bsp/device-tree/device
> > >> -
> > >> tree-generation_%.bbappend
> > >>
> > >> Parsing recipes..done.
> > >>
> > >> === Matching recipes: ===
> > >>
> > >> gcc:
> > >>
> > >>   meta-linaro-toolchain linaro-4.9
> > >>
> > >>   meta-linaro-toolchain linaro-6.2
> > >>
> > >>   meta                 6.2.0
> > >>
> > >>   meta                 5.4.0
> > >>
> > >>   meta-linaro-toolchain linaro-5.3
> > >>
> > >>   meta-linaro-toolchain linaro-5.2
> > >>
> > >>
> > >>
> > >> Immediately I have set the PREFERRED_VERSION of gcc to 4.9 but 
> > >> bitbake does not go beyond configuration.
> > >>
> > >>
> > >
> > > Please post the error and change you did to enable 4.9
> > >
> > >>
> > >> I believe 4.9 + morty combination has not been tested at all. I 
> > >> understand my apps need to get updated, but that’s not my call.
> > >
> > > OE-core and yocto releases by default do not test toolchains coming 
> > > from other layers so essentially 6.2 is whats the default compiler 
> > > with morty and thats what is most tested however, others might have 
> > > tested the other combinations with morty,
> > -- 
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: GCC 4.9 and Morty

[Lee, Yong]

Thanks Denys for the pointers. Have subscribed to meta-arago.
My questions will be more appropriately posted.

-----Original Message-----
From: Denys Dmytriyenko [mailto:denis@denix.org] 
Sent: Thursday, October 26, 2017 8:43 AM
To: Lee, Yong <Yong.Lee@johnsonoutdoors.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] GCC 4.9 and Morty

On Thu, Oct 26, 2017 at 08:25:00AM -0400, Denys Dmytriyenko wrote:
> On Tue, Oct 24, 2017 at 06:37:17PM +0000, Lee, Yong wrote:
> > Thank you.
> > I switched to internal toolchain and building GCC 5.4 (included in 
> > meta) is complete and is onto glibc.
> > 
> > In summary, TI SDK appears to be broken as the none-default GCC 
> > version included in their package (ie. Linaro 4.9 and Linaro 5.2) fails to build.
> 
> There's nothing wrong with TI SDK - the issue is often with the Linaro 
> prebuilt toolchain changing little things from version to version and 
> breaking corresponding recipes. Unfortunately, external toolchain is 
> required, hence I only support 1 specific Linaro toolchain version per 
> release - 7.x in rocko, 6.x in morty, 5.x in krogoth, 4.9 in fido, 
> etc. So, if you need a different Linaro toolchain version, either 
> switch to a corresponding release setup, or try porting those recipes.
> Alternatively, you can always switch to internal toolchain by simply 
> passing TOOLCHAIN_TYPE=internal to TI SDK build. It's not the default 
> and doesn't get tested very much against TI SDK, but I try to ensure 
> nothing is broken in each relesae. Though, gcc7 is still work in progress.

BTW, meta-arago has its own mailing list, as well as meta-linaro has one too. 
Complaining to OE-Core about specifics like this is like posting to LKML about issues with your Linux distro... As Khem said - ask your SDK provider. And maybe try doing that first - could probably save you a lot of headache...


> > -----Original Message-----
> > From: Khem Raj [mailto:raj.khem@gmail.com]
> > Sent: Tuesday, October 24, 2017 1:46 PM
> > To: Lee, Yong <Yong.Lee@johnsonoutdoors.com>
> > Cc: openembedded-core@lists.openembedded.org
> > Subject: Re: [OE-core] GCC 4.9 and Morty
> > 
> > On Tue, Oct 24, 2017 at 10:33 AM, Lee, Yong <Yong.Lee@johnsonoutdoors.com> wrote:
> > > Thanks Raj for the input. Attached the logs. Please take a look.
> > > The .diff file is based on the toolchain-linaro.inc file shipped with TI's SDK [1].
> > >
> > 
> > Your changes look fine.
> > 
> > > I will try to configure the SDK to use the internal toolchain and see if I can decouple myself from the external toolchain to simplify things.
> > >
> > 
> > you might have to bug your SDK provider for gcc 4.9 build issue
> > 
> > 
> > > Adam
> > >
> > > [1]
> > > http://arago-project.org/git/?p=meta-arago.git;a=blob;f=meta-arago
> > > -dis
> > > tro/conf/distro/include/toolchain-linaro.inc;h=20a65174f269c1e1a59
> > > 84c5 476a2ab4e5dfc42b5;hb=refs/heads/morty
> > >
> > > -----Original Message-----
> > > From: Khem Raj [mailto:raj.khem@gmail.com]
> > > Sent: Tuesday, October 24, 2017 12:26 PM
> > > To: Lee, Yong <Yong.Lee@johnsonoutdoors.com>
> > > Cc: openembedded-core@lists.openembedded.org
> > > Subject: Re: [OE-core] GCC 4.9 and Morty
> > >
> > > *EXTERNAL EMAIL*
> > >
> > >
> > > On Tue, Oct 24, 2017 at 6:56 AM, Lee, Yong <Yong.Lee@johnsonoutdoors.com> wrote:
> > >> I have a bunch of apps that require an old version of GCC (4.9 or less).
> > >>
> > >> There are a few versions of GCC available in my Morty based SDK.
> > >>
> > >>
> > >>
> > >> build@6e35408e8fa5:~/tisdk/build$ bitbake-layers show-recipes gcc
> > >>
> > >> WARNING: No recipes available for:
> > >>
> > >>
> > >> /home/build/tisdk/sources/meta-openamp/recipes-bsp/device-tree/de
> > >> vice
> > >> -
> > >> tree-generation_%.bbappend
> > >>
> > >> Parsing recipes..done.
> > >>
> > >> === Matching recipes: ===
> > >>
> > >> gcc:
> > >>
> > >>   meta-linaro-toolchain linaro-4.9
> > >>
> > >>   meta-linaro-toolchain linaro-6.2
> > >>
> > >>   meta                 6.2.0
> > >>
> > >>   meta                 5.4.0
> > >>
> > >>   meta-linaro-toolchain linaro-5.3
> > >>
> > >>   meta-linaro-toolchain linaro-5.2
> > >>
> > >>
> > >>
> > >> Immediately I have set the PREFERRED_VERSION of gcc to 4.9 but 
> > >> bitbake does not go beyond configuration.
> > >>
> > >>
> > >
> > > Please post the error and change you did to enable 4.9
> > >
> > >>
> > >> I believe 4.9 + morty combination has not been tested at all. I 
> > >> understand my apps need to get updated, but that’s not my call.
> > >
> > > OE-core and yocto releases by default do not test toolchains 
> > > coming from other layers so essentially 6.2 is whats the default 
> > > compiler with morty and thats what is most tested however, others 
> > > might have tested the other combinations with morty,
> > --
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core