external toolchain

external toolchain

[Dallas Clement]

I'm trying to use an external pre-built toolchain to build my distro.
I added a "TCMODE ?= "external-sourcery" to my local.conf and modified
the external-sourcery include file as follows:

diff --git a/meta/conf/distro/include/tcmode-external-sourcery.inc
b/meta/conf/distro/include/tcmode-external-source
index 1635eec..3ba564a 100644
--- a/meta/conf/distro/include/tcmode-external-sourcery.inc
+++ b/meta/conf/distro/include/tcmode-external-sourcery.inc
@@ -2,14 +2,16 @@
 # Configuration to use external Sourcery G++ toolchain
 #

-EXTERNAL_TOOLCHAIN ?= "/usr/local/csl/${TARGET_ARCH}"
+#EXTERNAL_TOOLCHAIN ?= "/usr/local/csl/${TARGET_ARCH}"
+EXTERNAL_TOOLCHAIN ?=
"/opt/armada-sdk-5.0-64k/armv7-marvell-linux-gnueabi-softfp"

 TOOLCHAIN_PATH_ADD = "${EXTERNAL_TOOLCHAIN}/bin:"
 PATH =. "${TOOLCHAIN_PATH_ADD}"

 CSL_TARGET_SYS_powerpc ?= "powerpc-linux-gnu"
 CSL_TARGET_SYS_powerpc64 ?= "powerpc-linux-gnu"
-CSL_TARGET_SYS_arm ?= "arm-none-linux-gnueabi"
+#CSL_TARGET_SYS_arm ?= "arm-none-linux-gnueabi"
+CSL_TARGET_SYS_arm ?= "arm-marvell-linux-gnueabi"
 CSL_TARGET_SYS_mips ?= "mips-linux-gnu"
 CSL_TARGET_SYS_mipsel ?= "mips-linux-gnu"
 CSL_TARGET_SYS_mips64 ?= "mips-linux-gnu"

bitbake is able to find my toolchain, but it eventually fails trying
to install the external sourcery toolchain for arm.

ERROR: Function failed: do_install (see
/development/dallasc/yocto/poky/build/tmp/work/armv5te-poky-linux-gnueabi/external-sourcery-toolchain-201111-0.-r7/temp/log.do_install.4466
for further information)
ERROR: Logfile of failure stored in:
/development/dallasc/yocto/poky/build/tmp/work/armv5te-poky-linux-gnueabi/external-sourcery-toolchain-201111-0.-r7/temp/log.do_install.4466
Log data follows:
| DEBUG: Executing shell function do_install
| ERROR: Function failed: do_install (see
/development/dallasc/yocto/poky/build/tmp/work/armv5te-poky-linux-gnueabi/external-sourcery-toolchain-201111-0.-r7/temp/log.do_install.4466
for further information)
| mv: cannot stat
`/development/dallasc/yocto/poky/build/tmp/work/armv5te-poky-linux-gnueabi/external-sourcery-toolchain-201111-0.-r7/image/usr/lib/bin/*':
No such file or directory
NOTE: package external-sourcery-toolchain-201111-0.-r7: task do_install: Failed
ERROR: Task 422
(/development/dallasc/yocto/poky/meta/recipes-core/meta/external-sourcery-toolchain.bb,
do_install) failed with exit code '1'

Should I be modifying this external-sourcery-toolchain recipe to point
to my toolchain sysroot area?  Just not sure what all needs to be done
to use my own toolchain.

Thanks

Re: external toolchain

[Chris Larson]

On Thu, Jul 12, 2012 at 12:20 PM, Dallas Clement
<dallas.a.clement@gmail.com> wrote:
> Should I be modifying this external-sourcery-toolchain recipe to point
> to my toolchain sysroot area?  Just not sure what all needs to be done
> to use my own toolchain.

This recipe is intended for use with the sourcery g++ toolchain. It's
not at all surprising that it might fail with one from a different
vendor. Modify the recipe as appropriate.
-- 
Christopher Larson

external toolchain

[Virgilia Eigner]

[-- Attachment #1: Type: text/html, Size: 8714 bytes --]

Re: external toolchain

[Khem Raj]

On Wed, Nov 18, 2015 at 1:26 AM, Virgilia  Eigner <Virgi200@gmx.de> wrote:
> In this case I can't find any help, has anyone an idea?

add a provider for gcc-source in your external toolchain recipe.

external toolchain

[Virgilia Eigner]

[-- Attachment #1: Type: text/html, Size: 3841 bytes --]

Re: External toolchain

[Khem Raj]

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


> On Oct 28, 2015, at 11:37 AM, Virgilia Eigner <virgi200@gmx.de> wrote:
> 
> Hi,
> 
> I am working on a image for my personal hardware.
> In this case I use to prefer my own toolchain (used before in buildroot).
> Now I am not sure how to proceed.
> Is it possible to include the old toolchain with a few chance setting in local.conf
> Or do i have to create my own Layer?
> How should i start with, are there some examples?
> 


you can hook in external toolchains, e.g. look at https://github.com/MentorEmbedded/meta-sourcery
for some guidance

> -Yocto Version YP Core-Dizzy 1.7.2
> -My own customize hardware, with different interfaces
> 
> 
> best regards Lisa
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

External toolchain

[Virgilia Eigner]

Hi,
 
I am working on a image for my personal hardware.
In this case I use to prefer my own toolchain (used before in buildroot).
Now I am not sure how to proceed. 
Is it possible to include the old toolchain with a few chance setting in local.conf
Or do i have to create my own Layer? 
How should i start with, are there some examples?
 
-Yocto Version YP Core-Dizzy 1.7.2
-My own customize hardware, with different interfaces
 
 
best regards Lisa

Re: External Toolchain

[Denys Dmytriyenko]

On Fri, Mar 28, 2014 at 03:50:29PM +0530, Anjandeep Sahni wrote:
> Hi all,
> 
> I am fairly new to poky. Just had a few queries.
> 
> I wanted to know where exactly in the build directory does poky
> build the default toolchain.
> And also if I have to use an external linaro toolchain, how would I
> go about it? Should I just include the meta-linaro layer, and add
> the TCMODE variable to local.conf?
> I downloaded and extracted the prebuilt binaries for linaro
> toolchain. How do I point my build system to use these instead of
> the default toolchain?

Anjandeep,

Please take a look at the presentation I gave at the last year ELC:

http://elinux.org/images/c/c8/ExternalToolchainsInYocto.pdf

Also, feel free to ping me directly at denys@ti.com if you are working on a 
project for TI - there's a lot of re-use potential...

-- 
Denys

External Toolchain

[Anjandeep Sahni]

Hi all,

I am fairly new to poky. Just had a few queries.

I wanted to know where exactly in the build directory does poky build 
the default toolchain.
And also if I have to use an external linaro toolchain, how would I go 
about it? Should I just include the meta-linaro layer, and add the 
TCMODE variable to local.conf?
I downloaded and extracted the prebuilt binaries for linaro toolchain. 
How do I point my build system to use these instead of the default 
toolchain?

-- 
Regards,
Anjandeep Sahni

Re: External toolchain

[Luca Bolognini]

Hi all,thank you to Denys and Khem for their replies.I would be glad to write a short wiki on "setting an external toolchain" topic but I think the route I followed is not the straightest one.In fact, as Denys underlined, I was wrong in modifying angstrom-2008.1.conf instead of local.conf, where I could have handled much less variables.I think it's quite better to put Denys reply in a FAQ, where everyone can access this info in the quickest way.As you have understood I engaged in putting an external toolchainin OE to get apache2 and modphp (still them!) in my Arago FS. I don't know if you have read my previous posts on the topic (I think it's extremely hard if it's all in one row, what a poor email client, sorry! :-( ), maybe you could help me?
Thank you,bye
Luca




----Messaggio originale----
Da: denis@denix.org
Data: 24/02/2011 5.07
A: <openembedded-devel@lists.openembedded.org>
Ogg: Re: [oe] External toolchain

On Wed, Feb 23, 2011 at 11:28:51AM -0800, Khem Raj wrote:
> On Wed, Feb 23, 2011 at 3:49 AM, Luca Bolognini <l.bolognini@tiscali.it> wrote:
> > Hi,thank you Ahsan for you reply.I solved my issue and I succeed in using external toolchain CodeSourcery2009q1 to cross-compile some packages in my OE 2010.12 release.However I didn't create any symlink of arm-angstrom-linux-gnueabi-gcc to arm-none-linux-gnueabi-gcc.I added an instantiation of TARGET_SYS variable to the hints of Denys and Tom (se reference link in my previous email).It's important to do so in order not to have errors in the do_install task of external-toolchain-csl.bb recipe.Then, as a resume, my openembedded/conf/distro/angstrom-2008.1.conf file changed in this way:
> > # Set the toolchain type (internal, external) and brand (generic, csl etc.)# LUCATARGET_VENDOR = "-none"TOOLCHAIN_TYPE ?= "external"TOOLCHAIN_BRAND ?= "csl"TOOLCHAIN_PATH = "/opt/ti/codesourcery"TARGET_SYS = "arm-none-linux-gnueabi"TOOLCHAIN_SYSPATH = "${TOOLCHAIN_PATH}/arm-none-linux-gnueabi"PATH_prepend = "${TOOLCHAIN_PATH}/bin:"require conf/distro/include/toolchain-external.inc
> > instead of
> > # Set the toolchain type (internal, external) and brand (generic, csl etc.)TOOLCHAIN_TYPE ?= "internal"TOOLCHAIN_BRAND ?= ""
> > Then it worked.Bye,Luca
> >

Luca,

Your MUA ate all the newlines and made your message into one long line, which 
is quite hard to read... :)

Anyway, you don't need to set TARGET_SYS manually, as it is composed from 
TARGET_ARCH, TARGET_VENDOR and TARGET_OS in bitbake.conf. Also, don't worry 
about TOOLCHAIN_SYSPATH - the default is also set there and is fine.

The reason you are having the issue you've mentioned, is because instead of 
adding those variables to your local.conf file, you are modifying 
angstrom-2008.1.conf, where placement is important - before or after the 
toolchain variables are handled.

Plus, more importantly, to overwrite distro's TARGET_VENDOR properly, you need 
to set TOOLCHAIN_VENDOR variable.

So, here's the minimum set of variables you need to set in your local.conf:

----------------------------------------------------
TOOLCHAIN_VENDOR = "-none"
TOOLCHAIN_TYPE = "external"
TOOLCHAIN_BRAND = "csl"

TOOLCHAIN_PATH = "/opt/arm-2009q1"
# If you don't have toolchain in system PATH, then:
PATH_prepend = "${TOOLCHAIN_PATH}/bin:"
----------------------------------------------------

Since you also mentioned Arago, you could have looked at how I set CSL in 
there by default (in arago.conf and toolchain-csl.conf files)...


> good it worked for you. Would you please document the steps you took
> from the beginning to get it working ?
> and send it as reply to this email ? We would like to add this into
> the wiki or FAQs

Tom and I have explained it many times already. I guess it's still hard to 
collect all the relevant info from separate posts on the mailing list.
Probably I should bite the bullet and create the necessary Wiki entry... :)

-- 
Denys



> > ----Messaggio originale----
> > Da: Noor_Ahsan@mentor.com
> > Data: 22/02/2011 10.47
> > A: <openembedded-devel@lists.openembedded.org>
> > Ogg: Re: [oe] External toolchain
> >
> > Hello Luca,
> >
> > Probably you need to create symbolic links of arm-angstrom-linux-
> > gnueabi-gcc to arm-none-linux-gnueabi-gcc. OE assumes that the compiler name is arm-angstrom-linux-gnueabi-gcc. You can see the "CC" variable value by take environment of libtool-cross (using -e options) that how OE is creating the name of compiler.
> >
> > Regards,
> > Noor
> >
> > -----Original Message-----
> > From: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Luca Bolognini
> > Sent: Tuesday, February 22, 2011 2:16 PM
> > To: Open Embedded Mailing List
> > Subject: [oe] External toolchain
> >
> > Hi,
> > I would like to use an external toolchain (CodeSourcery2009q1) to
> > cross-compile some packages for my beagleboard (more or less the same
> > that happens in Arago) and then I expect not to download glibc package
> > and cross-compile again libc, libpthread and so on. I would like to use
> > the libraries inside my external CodeSourcery SDK.
> > I followed some
> > hints by Denys and Tom ( http://lists.linuxtogo.
> > org/pipermail/openembedded-devel/2010-April/019521.html ) and I put
> >
> > #
> > LUCA
> > TARGET_VENDOR = "-none"
> > TOOLCHAIN_TYPE ?= "external"
> >
> > TOOLCHAIN_BRAND ?= "csl"
> > TOOLCHAIN_PATH = "/opt/ti/codesourcery"
> >
> > TOOLCHAIN_SYSPATH = "${TOOLCHAIN_PATH}/arm-none-linux-gnueabi"
> >
> > PATH_prepend = "${TOOLCHAIN_PATH}/bin:"
> > require
> > conf/distro/include/toolchain-external.inc
> >
> > inside my
> > openembedded/conf/distro/angstrom-2008.1.conf
> >
> > As you know, cross-
> > compiler provided by CodeSoucery is arm-none-linux-gnueabi-gcc but I
> > get the following error with libtool-cross_2.2.6b.bb:
> > Build
> > Configuration:
> > BB_VERSION        = "1.8.19"
> > METADATA_BRANCH   =
> > "release-2010.12"
> > METADATA_REVISION = "dec3967"
> > TARGET_ARCH       =
> > "arm"
> > TARGET_OS         = "linux-gnueabi"
> > MACHINE           =
> > "beagleboard"
> > DISTRO            = "angstrom"
> > DISTRO_VERSION    =
> > "2010.7-test-20110221"
> > TARGET_FPU        = "hard"
> > [...]
> > | checking for
> > arm-angstrom-linux-gnueabi-gcc... arm-angstrom-linux-gnueabi-gcc -
> > march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mthumb-
> > interwork -mno-thumb
> > | checking whether the C compiler works... no
> > |
> > configure: error: in `/home/bolognini/diskp2/diskp2.4/pure-
> > oe/build/tmp/work/armv7a-angstrom-linux-gnueabi/libtool-cross-2.2.6b-
> > r27.1/libtool-2.2.6b':
> > | configure: error: C compiler cannot create
> > executables
> >
> > Obviously OE doesn't have to find arm-angstrom-linux-
> > gnueabi-gcc, but why does it search for arm-angstrom-linux-gnueabi-gcc
> > instead of arm-none-linux-gnueabi-gcc ?
> > What's wrong inside angstrom-
> > 2008.1.conf or what am I missing?
> >
> > Thank you for your support
> > Luca
> >
> >
> > Supera i limiti: raddoppia la velocit?? da 10 a 20 Mega!   Risparmia con Tutto Incluso: telefono + adsl 20 mega a soli 29,95 ??? al mese per due anni!  SCONTO DI 240 EURO!  http://abbonati.tiscali.it/telefono-adsl/prodotti/tc/tuttoincluso/?WT.mc_id=01fw
> >
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> >
> >
> >
> >
> >
> > Supera i limiti: raddoppia la velocit?? da 10 a 20 Mega!
> > Risparmia con Tutto Incluso: telefono + adsl 20 mega a soli 29,95 ??? al mese per due anni!
> > SCONTO DI 240 EURO!
> > http://abbonati.tiscali.it/telefono-adsl/prodotti/tc/tuttoincluso/?WT.mc_id=01fw
> >
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> >
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel





Supera i limiti: raddoppia la velocità da 10 a 20 Mega! 
Risparmia con Tutto Incluso: telefono + adsl 20 mega a soli 29,95 € al mese per due anni!
SCONTO DI 240 EURO!
http://abbonati.tiscali.it/telefono-adsl/prodotti/tc/tuttoincluso/?WT.mc_id=01fw

Re: External toolchain

[Denys Dmytriyenko]

On Wed, Feb 23, 2011 at 11:28:51AM -0800, Khem Raj wrote:
> On Wed, Feb 23, 2011 at 3:49 AM, Luca Bolognini <l.bolognini@tiscali.it> wrote:
> > Hi,thank you Ahsan for you reply.I solved my issue and I succeed in using external toolchain CodeSourcery2009q1 to cross-compile some packages in my OE 2010.12 release.However I didn't create any symlink of arm-angstrom-linux-gnueabi-gcc to arm-none-linux-gnueabi-gcc.I added an instantiation of TARGET_SYS variable to the hints of Denys and Tom (se reference link in my previous email).It's important to do so in order not to have errors in the do_install task of external-toolchain-csl.bb recipe.Then, as a resume, my openembedded/conf/distro/angstrom-2008.1.conf file changed in this way:
> > # Set the toolchain type (internal, external) and brand (generic, csl etc.)# LUCATARGET_VENDOR = "-none"TOOLCHAIN_TYPE ?= "external"TOOLCHAIN_BRAND ?= "csl"TOOLCHAIN_PATH = "/opt/ti/codesourcery"TARGET_SYS = "arm-none-linux-gnueabi"TOOLCHAIN_SYSPATH = "${TOOLCHAIN_PATH}/arm-none-linux-gnueabi"PATH_prepend = "${TOOLCHAIN_PATH}/bin:"require conf/distro/include/toolchain-external.inc
> > instead of
> > # Set the toolchain type (internal, external) and brand (generic, csl etc.)TOOLCHAIN_TYPE ?= "internal"TOOLCHAIN_BRAND ?= ""
> > Then it worked.Bye,Luca
> >

Luca,

Your MUA ate all the newlines and made your message into one long line, which 
is quite hard to read... :)

Anyway, you don't need to set TARGET_SYS manually, as it is composed from 
TARGET_ARCH, TARGET_VENDOR and TARGET_OS in bitbake.conf. Also, don't worry 
about TOOLCHAIN_SYSPATH - the default is also set there and is fine.

The reason you are having the issue you've mentioned, is because instead of 
adding those variables to your local.conf file, you are modifying 
angstrom-2008.1.conf, where placement is important - before or after the 
toolchain variables are handled.

Plus, more importantly, to overwrite distro's TARGET_VENDOR properly, you need 
to set TOOLCHAIN_VENDOR variable.

So, here's the minimum set of variables you need to set in your local.conf:

----------------------------------------------------
TOOLCHAIN_VENDOR = "-none"
TOOLCHAIN_TYPE = "external"
TOOLCHAIN_BRAND = "csl"

TOOLCHAIN_PATH = "/opt/arm-2009q1"
# If you don't have toolchain in system PATH, then:
PATH_prepend = "${TOOLCHAIN_PATH}/bin:"
----------------------------------------------------

Since you also mentioned Arago, you could have looked at how I set CSL in 
there by default (in arago.conf and toolchain-csl.conf files)...


> good it worked for you. Would you please document the steps you took
> from the beginning to get it working ?
> and send it as reply to this email ? We would like to add this into
> the wiki or FAQs

Tom and I have explained it many times already. I guess it's still hard to 
collect all the relevant info from separate posts on the mailing list.
Probably I should bite the bullet and create the necessary Wiki entry... :)

-- 
Denys



> > ----Messaggio originale----
> > Da: Noor_Ahsan@mentor.com
> > Data: 22/02/2011 10.47
> > A: <openembedded-devel@lists.openembedded.org>
> > Ogg: Re: [oe] External toolchain
> >
> > Hello Luca,
> >
> > Probably you need to create symbolic links of arm-angstrom-linux-
> > gnueabi-gcc to arm-none-linux-gnueabi-gcc. OE assumes that the compiler name is arm-angstrom-linux-gnueabi-gcc. You can see the "CC" variable value by take environment of libtool-cross (using -e options) that how OE is creating the name of compiler.
> >
> > Regards,
> > Noor
> >
> > -----Original Message-----
> > From: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Luca Bolognini
> > Sent: Tuesday, February 22, 2011 2:16 PM
> > To: Open Embedded Mailing List
> > Subject: [oe] External toolchain
> >
> > Hi,
> > I would like to use an external toolchain (CodeSourcery2009q1) to
> > cross-compile some packages for my beagleboard (more or less the same
> > that happens in Arago) and then I expect not to download glibc package
> > and cross-compile again libc, libpthread and so on. I would like to use
> > the libraries inside my external CodeSourcery SDK.
> > I followed some
> > hints by Denys and Tom ( http://lists.linuxtogo.
> > org/pipermail/openembedded-devel/2010-April/019521.html ) and I put
> >
> > #
> > LUCA
> > TARGET_VENDOR = "-none"
> > TOOLCHAIN_TYPE ?= "external"
> >
> > TOOLCHAIN_BRAND ?= "csl"
> > TOOLCHAIN_PATH = "/opt/ti/codesourcery"
> >
> > TOOLCHAIN_SYSPATH = "${TOOLCHAIN_PATH}/arm-none-linux-gnueabi"
> >
> > PATH_prepend = "${TOOLCHAIN_PATH}/bin:"
> > require
> > conf/distro/include/toolchain-external.inc
> >
> > inside my
> > openembedded/conf/distro/angstrom-2008.1.conf
> >
> > As you know, cross-
> > compiler provided by CodeSoucery is arm-none-linux-gnueabi-gcc but I
> > get the following error with libtool-cross_2.2.6b.bb:
> > Build
> > Configuration:
> > BB_VERSION        = "1.8.19"
> > METADATA_BRANCH   =
> > "release-2010.12"
> > METADATA_REVISION = "dec3967"
> > TARGET_ARCH       =
> > "arm"
> > TARGET_OS         = "linux-gnueabi"
> > MACHINE           =
> > "beagleboard"
> > DISTRO            = "angstrom"
> > DISTRO_VERSION    =
> > "2010.7-test-20110221"
> > TARGET_FPU        = "hard"
> > [...]
> > | checking for
> > arm-angstrom-linux-gnueabi-gcc... arm-angstrom-linux-gnueabi-gcc -
> > march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mthumb-
> > interwork -mno-thumb
> > | checking whether the C compiler works... no
> > |
> > configure: error: in `/home/bolognini/diskp2/diskp2.4/pure-
> > oe/build/tmp/work/armv7a-angstrom-linux-gnueabi/libtool-cross-2.2.6b-
> > r27.1/libtool-2.2.6b':
> > | configure: error: C compiler cannot create
> > executables
> >
> > Obviously OE doesn't have to find arm-angstrom-linux-
> > gnueabi-gcc, but why does it search for arm-angstrom-linux-gnueabi-gcc
> > instead of arm-none-linux-gnueabi-gcc ?
> > What's wrong inside angstrom-
> > 2008.1.conf or what am I missing?
> >
> > Thank you for your support
> > Luca
> >
> >
> > Supera i limiti: raddoppia la velocit?? da 10 a 20 Mega!   Risparmia con Tutto Incluso: telefono + adsl 20 mega a soli 29,95 ??? al mese per due anni!  SCONTO DI 240 EURO!  http://abbonati.tiscali.it/telefono-adsl/prodotti/tc/tuttoincluso/?WT.mc_id=01fw
> >
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> >
> >
> >
> >
> >
> > Supera i limiti: raddoppia la velocit?? da 10 a 20 Mega!
> > Risparmia con Tutto Incluso: telefono + adsl 20 mega a soli 29,95 ??? al mese per due anni!
> > SCONTO DI 240 EURO!
> > http://abbonati.tiscali.it/telefono-adsl/prodotti/tc/tuttoincluso/?WT.mc_id=01fw
> >
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> >
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: External toolchain

[Khem Raj]

On Wed, Feb 23, 2011 at 3:49 AM, Luca Bolognini <l.bolognini@tiscali.it> wrote:
> Hi,thank you Ahsan for you reply.I solved my issue and I succeed in using external toolchain CodeSourcery2009q1 to cross-compile some packages in my OE 2010.12 release.However I didn't create any symlink of arm-angstrom-linux-gnueabi-gcc to arm-none-linux-gnueabi-gcc.I added an instantiation of TARGET_SYS variable to the hints of Denys and Tom (se reference link in my previous email).It's important to do so in order not to have errors in the do_install task of external-toolchain-csl.bb recipe.Then, as a resume, my openembedded/conf/distro/angstrom-2008.1.conf file changed in this way:
> # Set the toolchain type (internal, external) and brand (generic, csl etc.)# LUCATARGET_VENDOR = "-none"TOOLCHAIN_TYPE ?= "external"TOOLCHAIN_BRAND ?= "csl"TOOLCHAIN_PATH = "/opt/ti/codesourcery"TARGET_SYS = "arm-none-linux-gnueabi"TOOLCHAIN_SYSPATH = "${TOOLCHAIN_PATH}/arm-none-linux-gnueabi"PATH_prepend = "${TOOLCHAIN_PATH}/bin:"require conf/distro/include/toolchain-external.inc
> instead of
> # Set the toolchain type (internal, external) and brand (generic, csl etc.)TOOLCHAIN_TYPE ?= "internal"TOOLCHAIN_BRAND ?= ""
> Then it worked.Bye,Luca
>

good it worked for you. Would you please document the steps you took
from the beginning to get it working ?
and send it as reply to this email ? We would like to add this into
the wiki or FAQs

Thanks for your help
-Khem

>
>
> ----Messaggio originale----
> Da: Noor_Ahsan@mentor.com
> Data: 22/02/2011 10.47
> A: <openembedded-devel@lists.openembedded.org>
> Ogg: Re: [oe] External toolchain
>
> Hello Luca,
>
> Probably you need to create symbolic links of arm-angstrom-linux-
> gnueabi-gcc to arm-none-linux-gnueabi-gcc. OE assumes that the compiler name is arm-angstrom-linux-gnueabi-gcc. You can see the "CC" variable value by take environment of libtool-cross (using -e options) that how OE is creating the name of compiler.
>
> Regards,
> Noor
>
> -----Original Message-----
> From: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Luca Bolognini
> Sent: Tuesday, February 22, 2011 2:16 PM
> To: Open Embedded Mailing List
> Subject: [oe] External toolchain
>
> Hi,
> I would like to use an external toolchain (CodeSourcery2009q1) to
> cross-compile some packages for my beagleboard (more or less the same
> that happens in Arago) and then I expect not to download glibc package
> and cross-compile again libc, libpthread and so on. I would like to use
> the libraries inside my external CodeSourcery SDK.
> I followed some
> hints by Denys and Tom ( http://lists.linuxtogo.
> org/pipermail/openembedded-devel/2010-April/019521.html ) and I put
>
> #
> LUCA
> TARGET_VENDOR = "-none"
> TOOLCHAIN_TYPE ?= "external"
>
> TOOLCHAIN_BRAND ?= "csl"
> TOOLCHAIN_PATH = "/opt/ti/codesourcery"
>
> TOOLCHAIN_SYSPATH = "${TOOLCHAIN_PATH}/arm-none-linux-gnueabi"
>
> PATH_prepend = "${TOOLCHAIN_PATH}/bin:"
> require
> conf/distro/include/toolchain-external.inc
>
> inside my
> openembedded/conf/distro/angstrom-2008.1.conf
>
> As you know, cross-
> compiler provided by CodeSoucery is arm-none-linux-gnueabi-gcc but I
> get the following error with libtool-cross_2.2.6b.bb:
> Build
> Configuration:
> BB_VERSION        = "1.8.19"
> METADATA_BRANCH   =
> "release-2010.12"
> METADATA_REVISION = "dec3967"
> TARGET_ARCH       =
> "arm"
> TARGET_OS         = "linux-gnueabi"
> MACHINE           =
> "beagleboard"
> DISTRO            = "angstrom"
> DISTRO_VERSION    =
> "2010.7-test-20110221"
> TARGET_FPU        = "hard"
> [...]
> | checking for
> arm-angstrom-linux-gnueabi-gcc... arm-angstrom-linux-gnueabi-gcc -
> march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mthumb-
> interwork -mno-thumb
> | checking whether the C compiler works... no
> |
> configure: error: in `/home/bolognini/diskp2/diskp2.4/pure-
> oe/build/tmp/work/armv7a-angstrom-linux-gnueabi/libtool-cross-2.2.6b-
> r27.1/libtool-2.2.6b':
> | configure: error: C compiler cannot create
> executables
>
> Obviously OE doesn't have to find arm-angstrom-linux-
> gnueabi-gcc, but why does it search for arm-angstrom-linux-gnueabi-gcc
> instead of arm-none-linux-gnueabi-gcc ?
> What's wrong inside angstrom-
> 2008.1.conf or what am I missing?
>
> Thank you for your support
> Luca
>
>
> Supera i limiti: raddoppia la velocità da 10 a 20 Mega!   Risparmia con Tutto Incluso: telefono + adsl 20 mega a soli 29,95 € al mese per due anni!  SCONTO DI 240 EURO!  http://abbonati.tiscali.it/telefono-adsl/prodotti/tc/tuttoincluso/?WT.mc_id=01fw
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
>
>
>
>
> Supera i limiti: raddoppia la velocità da 10 a 20 Mega!
> Risparmia con Tutto Incluso: telefono + adsl 20 mega a soli 29,95 € al mese per due anni!
> SCONTO DI 240 EURO!
> http://abbonati.tiscali.it/telefono-adsl/prodotti/tc/tuttoincluso/?WT.mc_id=01fw
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: External toolchain

[Luca Bolognini]

Hi,thank you Ahsan for you reply.I solved my issue and I succeed in using external toolchain CodeSourcery2009q1 to cross-compile some packages in my OE 2010.12 release.However I didn't create any symlink of arm-angstrom-linux-gnueabi-gcc to arm-none-linux-gnueabi-gcc.I added an instantiation of TARGET_SYS variable to the hints of Denys and Tom (se reference link in my previous email).It's important to do so in order not to have errors in the do_install task of external-toolchain-csl.bb recipe.Then, as a resume, my openembedded/conf/distro/angstrom-2008.1.conf file changed in this way:
# Set the toolchain type (internal, external) and brand (generic, csl etc.)# LUCATARGET_VENDOR = "-none"TOOLCHAIN_TYPE ?= "external"TOOLCHAIN_BRAND ?= "csl"TOOLCHAIN_PATH = "/opt/ti/codesourcery"TARGET_SYS = "arm-none-linux-gnueabi"TOOLCHAIN_SYSPATH = "${TOOLCHAIN_PATH}/arm-none-linux-gnueabi"PATH_prepend = "${TOOLCHAIN_PATH}/bin:"require conf/distro/include/toolchain-external.inc
instead of
# Set the toolchain type (internal, external) and brand (generic, csl etc.)TOOLCHAIN_TYPE ?= "internal"TOOLCHAIN_BRAND ?= ""
Then it worked.Bye,Luca



----Messaggio originale----
Da: Noor_Ahsan@mentor.com
Data: 22/02/2011 10.47
A: <openembedded-devel@lists.openembedded.org>
Ogg: Re: [oe] External toolchain

Hello Luca,

Probably you need to create symbolic links of arm-angstrom-linux-
gnueabi-gcc to arm-none-linux-gnueabi-gcc. OE assumes that the compiler name is arm-angstrom-linux-gnueabi-gcc. You can see the "CC" variable value by take environment of libtool-cross (using -e options) that how OE is creating the name of compiler.

Regards,
Noor

-----Original Message-----
From: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Luca Bolognini
Sent: Tuesday, February 22, 2011 2:16 PM
To: Open Embedded Mailing List
Subject: [oe] External toolchain

Hi,
I would like to use an external toolchain (CodeSourcery2009q1) to 
cross-compile some packages for my beagleboard (more or less the same 
that happens in Arago) and then I expect not to download glibc package 
and cross-compile again libc, libpthread and so on. I would like to use 
the libraries inside my external CodeSourcery SDK.
I followed some 
hints by Denys and Tom ( http://lists.linuxtogo.
org/pipermail/openembedded-devel/2010-April/019521.html ) and I put 

# 
LUCA
TARGET_VENDOR = "-none"
TOOLCHAIN_TYPE ?= "external"

TOOLCHAIN_BRAND ?= "csl"
TOOLCHAIN_PATH = "/opt/ti/codesourcery"

TOOLCHAIN_SYSPATH = "${TOOLCHAIN_PATH}/arm-none-linux-gnueabi"

PATH_prepend = "${TOOLCHAIN_PATH}/bin:"
require 
conf/distro/include/toolchain-external.inc

inside my 
openembedded/conf/distro/angstrom-2008.1.conf

As you know, cross-
compiler provided by CodeSoucery is arm-none-linux-gnueabi-gcc but I 
get the following error with libtool-cross_2.2.6b.bb:
Build 
Configuration:
BB_VERSION        = "1.8.19"
METADATA_BRANCH   = 
"release-2010.12"
METADATA_REVISION = "dec3967"
TARGET_ARCH       = 
"arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = 
"beagleboard"
DISTRO            = "angstrom"
DISTRO_VERSION    = 
"2010.7-test-20110221"
TARGET_FPU        = "hard"
[...]
| checking for 
arm-angstrom-linux-gnueabi-gcc... arm-angstrom-linux-gnueabi-gcc -
march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mthumb-
interwork -mno-thumb
| checking whether the C compiler works... no
| 
configure: error: in `/home/bolognini/diskp2/diskp2.4/pure-
oe/build/tmp/work/armv7a-angstrom-linux-gnueabi/libtool-cross-2.2.6b-
r27.1/libtool-2.2.6b':
| configure: error: C compiler cannot create 
executables

Obviously OE doesn't have to find arm-angstrom-linux-
gnueabi-gcc, but why does it search for arm-angstrom-linux-gnueabi-gcc 
instead of arm-none-linux-gnueabi-gcc ?
What's wrong inside angstrom-
2008.1.conf or what am I missing?

Thank you for your support
Luca


Supera i limiti: raddoppia la velocità da 10 a 20 Mega!   Risparmia con Tutto Incluso: telefono + adsl 20 mega a soli 29,95 € al mese per due anni!  SCONTO DI 240 EURO!  http://abbonati.tiscali.it/telefono-adsl/prodotti/tc/tuttoincluso/?WT.mc_id=01fw 

_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel





Supera i limiti: raddoppia la velocità da 10 a 20 Mega! 
Risparmia con Tutto Incluso: telefono + adsl 20 mega a soli 29,95 € al mese per due anni!
SCONTO DI 240 EURO!
http://abbonati.tiscali.it/telefono-adsl/prodotti/tc/tuttoincluso/?WT.mc_id=01fw

Re: External toolchain

[Ahsan, Noor]

Hello Luca,

Probably you need to create symbolic links of arm-angstrom-linux-
gnueabi-gcc to arm-none-linux-gnueabi-gcc. OE assumes that the compiler name is arm-angstrom-linux-gnueabi-gcc. You can see the "CC" variable value by take environment of libtool-cross (using -e options) that how OE is creating the name of compiler.

Regards,
Noor

-----Original Message-----
From: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Luca Bolognini
Sent: Tuesday, February 22, 2011 2:16 PM
To: Open Embedded Mailing List
Subject: [oe] External toolchain

Hi,
I would like to use an external toolchain (CodeSourcery2009q1) to 
cross-compile some packages for my beagleboard (more or less the same 
that happens in Arago) and then I expect not to download glibc package 
and cross-compile again libc, libpthread and so on. I would like to use 
the libraries inside my external CodeSourcery SDK.
I followed some 
hints by Denys and Tom ( http://lists.linuxtogo.
org/pipermail/openembedded-devel/2010-April/019521.html ) and I put 

# 
LUCA
TARGET_VENDOR = "-none"
TOOLCHAIN_TYPE ?= "external"

TOOLCHAIN_BRAND ?= "csl"
TOOLCHAIN_PATH = "/opt/ti/codesourcery"

TOOLCHAIN_SYSPATH = "${TOOLCHAIN_PATH}/arm-none-linux-gnueabi"

PATH_prepend = "${TOOLCHAIN_PATH}/bin:"
require 
conf/distro/include/toolchain-external.inc

inside my 
openembedded/conf/distro/angstrom-2008.1.conf

As you know, cross-
compiler provided by CodeSoucery is arm-none-linux-gnueabi-gcc but I 
get the following error with libtool-cross_2.2.6b.bb:
Build 
Configuration:
BB_VERSION        = "1.8.19"
METADATA_BRANCH   = 
"release-2010.12"
METADATA_REVISION = "dec3967"
TARGET_ARCH       = 
"arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = 
"beagleboard"
DISTRO            = "angstrom"
DISTRO_VERSION    = 
"2010.7-test-20110221"
TARGET_FPU        = "hard"
[...]
| checking for 
arm-angstrom-linux-gnueabi-gcc... arm-angstrom-linux-gnueabi-gcc -
march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mthumb-
interwork -mno-thumb
| checking whether the C compiler works... no
| 
configure: error: in `/home/bolognini/diskp2/diskp2.4/pure-
oe/build/tmp/work/armv7a-angstrom-linux-gnueabi/libtool-cross-2.2.6b-
r27.1/libtool-2.2.6b':
| configure: error: C compiler cannot create 
executables

Obviously OE doesn't have to find arm-angstrom-linux-
gnueabi-gcc, but why does it search for arm-angstrom-linux-gnueabi-gcc 
instead of arm-none-linux-gnueabi-gcc ?
What's wrong inside angstrom-
2008.1.conf or what am I missing?

Thank you for your support
Luca


Supera i limiti: raddoppia la velocità da 10 a 20 Mega!   Risparmia con Tutto Incluso: telefono + adsl 20 mega a soli 29,95 € al mese per due anni!  SCONTO DI 240 EURO!  http://abbonati.tiscali.it/telefono-adsl/prodotti/tc/tuttoincluso/?WT.mc_id=01fw 

_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

External toolchain

[Luca Bolognini]

Hi,
I would like to use an external toolchain (CodeSourcery2009q1) to 
cross-compile some packages for my beagleboard (more or less the same 
that happens in Arago) and then I expect not to download glibc package 
and cross-compile again libc, libpthread and so on. I would like to use 
the libraries inside my external CodeSourcery SDK.
I followed some 
hints by Denys and Tom ( http://lists.linuxtogo.
org/pipermail/openembedded-devel/2010-April/019521.html ) and I put 

# 
LUCA
TARGET_VENDOR = "-none"
TOOLCHAIN_TYPE ?= "external"

TOOLCHAIN_BRAND ?= "csl"
TOOLCHAIN_PATH = "/opt/ti/codesourcery"

TOOLCHAIN_SYSPATH = "${TOOLCHAIN_PATH}/arm-none-linux-gnueabi"

PATH_prepend = "${TOOLCHAIN_PATH}/bin:"
require 
conf/distro/include/toolchain-external.inc

inside my 
openembedded/conf/distro/angstrom-2008.1.conf

As you know, cross-
compiler provided by CodeSoucery is arm-none-linux-gnueabi-gcc but I 
get the following error with libtool-cross_2.2.6b.bb:
Build 
Configuration:
BB_VERSION        = "1.8.19"
METADATA_BRANCH   = 
"release-2010.12"
METADATA_REVISION = "dec3967"
TARGET_ARCH       = 
"arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = 
"beagleboard"
DISTRO            = "angstrom"
DISTRO_VERSION    = 
"2010.7-test-20110221"
TARGET_FPU        = "hard"
[...]
| checking for 
arm-angstrom-linux-gnueabi-gcc... arm-angstrom-linux-gnueabi-gcc -
march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mthumb-
interwork -mno-thumb
| checking whether the C compiler works... no
| 
configure: error: in `/home/bolognini/diskp2/diskp2.4/pure-
oe/build/tmp/work/armv7a-angstrom-linux-gnueabi/libtool-cross-2.2.6b-
r27.1/libtool-2.2.6b':
| configure: error: C compiler cannot create 
executables

Obviously OE doesn't have to find arm-angstrom-linux-
gnueabi-gcc, but why does it search for arm-angstrom-linux-gnueabi-gcc 
instead of arm-none-linux-gnueabi-gcc ?
What's wrong inside angstrom-
2008.1.conf or what am I missing?

Thank you for your support
Luca


Supera i limiti: raddoppia la velocità da 10 a 20 Mega!   Risparmia con Tutto Incluso: telefono + adsl 20 mega a soli 29,95 € al mese per due anni!  SCONTO DI 240 EURO!  http://abbonati.tiscali.it/telefono-adsl/prodotti/tc/tuttoincluso/?WT.mc_id=01fw