which arm cross compile we used in yocto

[fulinux]

Dear community,

i find cross compile "arm-poky-linux-gnueabi-gcc" in fsl-release-bsp, the command results shows many cross compile as following, which one we used? and what others to do?

[fulinux@ubuntu tmp]$ find -name arm-poky-linux-gnueabi-gcc

./work/x86_64-linux/gcc-cross-arm/5.2.0-r0/image/home/fulinux/fsl-release-bsp/build-fb/tmp/sysroots/x86_64-linux/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc

./work/x86_64-linux/gcc-cross-arm/5.2.0-r0/image/home/fulinux/fsl-release-bsp/build-fb/tmp/sysroots/x86_64-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/5.2.0/arm-poky-linux-gnueabi-gcc

./work/x86_64-linux/gcc-cross-arm/5.2.0-r0/sysroot-destdir/home/fulinux/fsl-release-bsp/build-fb/tmp/sysroots/x86_64-linux/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc

./work/x86_64-linux/gcc-cross-arm/5.2.0-r0/sysroot-destdir/home/fulinux/fsl-release-bsp/build-fb/tmp/sysroots/x86_64-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/5.2.0/arm-poky-linux-gnueabi-gcc

./work/x86_64-linux/gcc-cross-initial-arm/5.2.0-r0/image/home/fulinux/fsl-release-bsp/build-fb/tmp/sysroots/x86_64-linux/usr/bin/arm-poky-linux-gnueabi.gcc-cross-initial-arm/arm-poky-linux-gnueabi-gcc

./work/x86_64-linux/gcc-cross-initial-arm/5.2.0-r0/sysroot-destdir/home/fulinux/fsl-release-bsp/build-fb/tmp/sysroots/x86_64-linux/usr/bin/arm-poky-linux-gnueabi.gcc-cross-initial-arm/arm-poky-linux-gnueabi-gcc

./sysroots/x86_64-linux/usr/bin/arm-poky-linux-gnueabi.gcc-cross-initial-arm/arm-poky-linux-gnueabi-gcc

./sysroots/x86_64-linux/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc

./sysroots/x86_64-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/5.2.0/arm-poky-linux-gnueabi-gcc

[pranavmadhu]

hi,

What I have read from yocto manual is

"Another feature for the SDKs is that only one set of cross-compiler toolchain binaries are produced per architecture. This feature takes advantage of the fact that the target hardware can be passed to gcc as a set of compiler options. Those options are set up by the environment script and contained in variables such as CC and LD. This reduces the space needed for the tools. Understand, however, that a sysroot is still needed for every target since those binaries are target-specific."

[fulinux]

Too hard to understand. where is it set CC and LD for uboot or kernel?

[pranavmadhu]

hi,

I think, you can use this binary for cross compile.

./work/x86_64-linux/gcc-cross-arm/5.2.0-r0/sysroot-destdir/home/fulinux/fsl-release-bsp/build-fb/tmp/sysroots/x86_64-linux/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc

If this does not work,try

./work/x86_64-linux/gcc-cross-arm/5.2.0-r0/image/home/fulinux/fsl-release-bsp/build-fb/tmp/sysroots/x86_64-linux/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc

With regards,

Pranav

[fulinux]

Hi Pranav,

there are both work, but why? why does yocto has many complies?

[b36401]

You can use "which arm-poky-linux-gnueabi-gcc" to find actual binary.

Have a great day,

Victor

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

[zoy74758]

For me, arm-poky-linux-gnueabi-gcc is not installed at all.

How can I install it? Looks like there is not such an application in the repo at all

Shell
apt search arm-poky-linux-gnueabi-gcc

[fulinux]

Dear Victor,

[fulinux@ubuntu fsl-release-bsp]$ source setup-environment build-fb

Welcome to Freescale Community BSP

The Yocto Project has extensive documentation about OE including a

reference manual which can be found at:

    http://yoctoproject.org/documentation

For more information about OpenEmbedded see their website:

    http://www.openembedded.org/

You can now run 'bitbake <target>'

Common targets are:

    core-image-minimal

    meta-toolchain

    meta-toolchain-sdk

    adt-installer

    meta-ide-support

Your configuration files at build-fb have not been touched.

[fulinux@ubuntu build-fb]$ arm-poky-linux-gnueabi-gcc     

arm-poky-linux-gnueabi-gcc：find command

[fulinux@ubuntu build-fb]$ which arm-poky-linux-gnueabi-gcc

it can't find command. may be "source setup-environment" can't export compile env value.