openembedded with a prebuilt external toolchain
Hi,
I'm trying to use openembedded with an external prebuilt toolchain. The docs at http://docs.openembedded.org/usermanual/usermanual.html mark this as TODO so maybe we can "do" that in this email chain. :)
Marvell provides a *.tar.gz with gcc and C libraries, which I've uncompressed somewhere in my home directory. My goal is to build a root filesystem with some assortment of packages, but at this point I'm just trying "bitbake nano" which is the very first example in the Getting Started. That seems like a logical start to board bring-up.
I'm assuming that I need to add some lines to build/conf/local.conf that tell OE to make no attempt at building its own compiler or C library (it can't anyway, it doesn't know my chip!) and to call my pre-built one instead. It looks like I'd want to add a few lines about TOOLCHAIN_*, but that uses a recipe for external toolchain, which assumes that it has some meta toolchain, and I'm floundering and getting nowhere. Couldn't find any of these magic variables documented in the usermanual so I've been digging through recipes to learn any of this.
Is it possible to add a few lines that tell OE the path and filename of my compiler? Or is it more complicated than that?
-joey
Quoted 21 lines · Joey Oravec
Hi,
I'm trying to use openembedded with an external prebuilt toolchain. The docs at http://docs.openembedded.org/usermanual/usermanual.html mark this as TODO so maybe we can "do" that in this email chain. :)
Marvell provides a *.tar.gz with gcc and C libraries, which I've uncompressed somewhere in my home directory. My goal is to build a root filesystem with some assortment of packages, but at this point I'm just trying "bitbake nano" which is the very first example in the Getting Started. That seems like a logical start to board bring-up.
I'm assuming that I need to add some lines to
build/conf/local.confthat tell OE to make no attempt at building its own compiler or C library (it can't anyway, it doesn't know my chip!) and to call my pre-built one instead. It looks like I'd want to add a few lines about TOOLCHAIN_*, but that uses a recipe for external toolchain, which assumes that it has some meta toolchain, and I'm floundering and getting nowhere. Couldn't find any of these magic variables documented in the usermanual so I've been digging through recipes to learn any of this.
Quoted 2 lines
Is it possible to add a few lines that tell OE the path and filename of my compiler? Or is it more complicated than that?
We talked about this a little on IRC and I provided the example of how to use the CodeSourcery recipes that exist today. The marvell toolchain however will need it's own special love. To start with, using the CSL recipe is roughly:
### CSL public ARM does <arch>-none-linux, so fill in the -none.
#TOOLCHAIN_VENDOR = "-none"
### CSL public ia32 does i686-pc-linux, so fill in the -pc.
#TOOLCHAIN_VENDOR = "-pc"
#### Bring in external-toolchain-csl.bb
#TOOLCHAIN_BRAND = "csl"
#TOOLCHAIN_TYPE = "external"
### Where the CSL version is installed. #TOOLCHAIN_PATH = "/scratch/ia32-2010.09"
### Where inside the CSL install the target libraries exist. #TOOLCHAIN_SYSPATH = "${TOOLCHAIN_PATH}/i686-pc-linux-gnu" ### Add tools to the PATH automatically. #PATH_prepend = "${TOOLCHAIN_PATH}/bin:"
Now what you'll want to do is make an external-toolchain-marvell.bb and set TOOLCHAIN_BRAND to "marvell" and tweak TOOLCHAIN_VENDOR such that we go from what OE normally says TARGET_SYS is to what your tools actually say it is. Then it's a matter of tweaking the contents of external-toolchain-marvell.bb to copy the right things out of the marvell install and into where OE wants them. In this regard, the -csl recipe may be more instructive than the -generic recipe as the -generic recipe (along with external-toolchain.bb) are targeted at toolchains exported by OE and thus require little mangling to work.
Signature · 2 lines
Tom Rini Mentor Graphics Corporation
Quoted 1 line · Tom Rini
We talked about this a little on IRC and I provided the example of how to use the CodeSourcery recipes that exist today. The marvell toolchain however will need it's own special love.
Yes! Much appreciated!
Quoted 4 lines
Now what you'll want to do is make an external-toolchain-marvell.bb and set
TOOLCHAIN_BRANDto "marvell" and tweakTOOLCHAIN_VENDORsuch that we go from what OE normally saysTARGET_SYSis to what your tools actually say it is. Then it's a matter of tweaking the contents of external-toolchain-marvell.bb to copy the right things out of the marvell install and into where OE wants them. In this regard, the(quoted diff) +0
-2-csl recipe may be more instructive than the -generic recipe as the -generic recipe (along with external-toolchain.bb) are targeted attoolchains exported by OE and thus require little mangling to work.
Both the -csl.bb and -generic.bb copy a bunch of stuff to STAGING_DIR in do_stage(). Of course in the long-run I need for the recipe to copy C libraries, but for now I should be able to leave the body blank. At least it'll use my compiler and run to completion. Right?
That's what I did and it seems to be ok. The "bitbake nano" example failed, looks like it wasn't linking ncurses. Another attempt with "bitbake busybox" worked and I saw some packages in the output folder. Looks good so far!
-joey
Quoted 17 lines · Joey Oravec
Quoted 3 lines · Tom Rini
We talked about this a little on IRC and I provided the example of how to use the CodeSourcery recipes that exist today. The marvell toolchain however will need it's own special love.
Yes! Much appreciated!
Quoted 9 lines
Now what you'll want to do is make an external-toolchain-marvell.bb and set
TOOLCHAIN_BRANDto "marvell" and tweakTOOLCHAIN_VENDORsuch that we go from what OE normally saysTARGET_SYSis to what your tools actually say it is. Then it's a matter of tweaking the contents of external-toolchain-marvell.bb to copy the right things out of the marvell install and into where OE wants them. In this regard, the -csl recipe may be more instructive than the -generic recipe as the -generic recipe (along with external-toolchain.bb) are targeted at toolchains exported by OE and thus require little mangling to work.
Quoted 4 lines
Both the -csl.bb and -generic.bb copy a bunch of stuff to
STAGING_DIRindo_stage(). Of course in the long-run I need for the recipe to copy C libraries, but for now I should be able to leave the body blank. At least it'll use my compiler and run to completion. Right?
Well, as you saw, it fails in some cases. This is because, yeah, we're telling the toolchain stuff lives ...here now, and it doesn't.
Quoted 4 lines
That's what I did and it seems to be ok. The "bitbake nano" example failed, looks like it wasn't linking ncurses. Another attempt with "bitbake busybox" worked and I saw some packages in the output folder. Looks good so far!
busybox, being self contained is more likely to be OK.
Signature · 2 lines
Tom Rini Mentor Graphics Corporation
Quoted 6 lines · Tom Rini
Quoted 4 lines
Both the -csl.bb and -generic.bb copy a bunch of stuff to
STAGING_DIRindo_stage(). Of course in the long-run I need for the recipe to copy C libraries, but for now I should be able to leave the body blank. At least it'll use my compiler and run to completion. Right?Well, as you saw, it fails in some cases. This is because, yeah, we're telling the toolchain stuff lives ...here now, and it doesn't.
Thanks for the additional help on chat! This followup is to share my results with the mailing list.
Regarding my "bitbake nano" failure, that was a symptom of a sysroot issue. An external cross compiler has some default sysroot where it looks for libraries. By default it looks like OE passes nothing to change this. As a result do_configure() didn't look for libraries in staging dir, decided that ncurses didn't exist, and the build failed. One solution is to add:
TOOLCHAIN_OPTIONS = " --sysroot=${STAGING_DIR_TARGET}"
to your build/conf/local.conf and make sure your compiler's default sysroot (libc, etc) gets copied into the staging dir. That way you can call *-gcc from somewhere in your path but it'll look for everything under OE's staging directory.
-joey
Quoted 12 lines · Joey Oravec
Quoted 7 lines · Tom Rini
Quoted 4 lines
Both the -csl.bb and -generic.bb copy a bunch of stuff to
STAGING_DIRindo_stage(). Of course in the long-run I need for the recipe to copy C libraries, but for now I should be able to leave the body blank. At least it'll use my compiler and run to completion. Right?Well, as you saw, it fails in some cases. This is because, yeah, we're telling the toolchain stuff lives ...here now, and it doesn't.
Thanks for the additional help on chat! This followup is to share my results with the mailing list.
Quoted 7 lines
Regarding my "bitbake nano" failure, that was a symptom of a sysroot issue. An external cross compiler has some default sysroot where it looks for libraries. By default it looks like OE passes nothing to change this. As a result
do_configure()didn't look for libraries in staging dir, decided that ncurses didn't exist, and the build failed. One solution is to add:
TOOLCHAIN_OPTIONS= " --sysroot=${STAGING_DIR_TARGET}"
That is the default now in conf/bitbake.conf:
Quoted 4 lines
to your
build/conf/local.confand make sure your compiler's default sysroot (libc, etc) gets copied into the staging dir. That way you can call *-gcc from somewhere in your path but it'll look for everything under OE's staging directory.
Signature · 1 line
Denys