Which Toolchain is being used to build Yocto ?

Which Toolchain is being used to build Yocto ?

[Mark T]

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

Hi,

Building jethro on a Ubuntu14.04 system. I want to ensure that each person
in the team is using the same tool-chain version.

I notice there is a meta/recipes-devtools  -  I assume this pulls in from
build/downloads - so gcc-5.2.0.tar.bz2 for example. Does the tool-chain
comprised of these recipes get built by /usr/bin/gcc before being used to
compile Yocto ?

If this is the case then assuming we configure for off-line builds and used
the same build/downloads content as well as the oe-env ( from
oe-init-build-env ) then we'll all be on the same tool-chain version. Or
have I missed something ?

Thanks,
Mark

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

Re: Which Toolchain is being used to build Yocto ?

[Kosta Zertsekel]

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

Mark,


>> I notice there is a meta/recipes-devtools  -  I assume this pulls in from build/downloads

>> - so gcc-5.2.0.tar.bz2 for example. Does the tool-chain comprised of these recipes get

>> built by /usr/bin/gcc before being used to compile Yocto?


You can easily check it by moving temporary /usr/bin/gcc aside.

BTW, provide the result of this test to the mailing list - so all of us can be synced.


--- KostaZ

[E-Banner]<http://www.mrv.com/blog>


MRV Communications is a global supplier of packet and optical solutions that power the world's largest networks. Our products combine innovative hardware with intelligent software to make networks smarter, faster and more efficient.



The contents of this message, together with any attachments, are intended only for the use of the person(s) to whom they are addressed and may contain confidential and/or privileged information. If you are not the intended recipient, immediately advise the sender, delete this message and any attachments and note that any distribution, or copying of this message, or any attachment, is prohibited.

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

Re: Which Toolchain is being used to build Yocto ?

[Burton, Ross]

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

On 3 February 2016 at 15:07, Mark T <mtl1nuxd3v@gmail.com> wrote:

> I notice there is a meta/recipes-devtools  -  I assume this pulls in from
> build/downloads - so gcc-5.2.0.tar.bz2 for example. Does the tool-chain
> comprised of these recipes get built by /usr/bin/gcc before being used to
> compile Yocto ?
>

The host's gcc (typically /usr/bin/gcc) is used to build gcc-cross, which
is then used to compile everything that needs to be cross-compiled.  We
don't build our own native compiler to replace the host compiler.

Ross

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

Re: Which Toolchain is being used to build Yocto ?

[Mark T]

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

Thanks. That makes sense; all the cross compile tools are built using the
Host machines native toolchain on the host then the cross-toolchain used to
cross compile yocto for the target.



On 3 February 2016 at 17:13, Burton, Ross <ross.burton@intel.com> wrote:

>
> On 3 February 2016 at 15:07, Mark T <mtl1nuxd3v@gmail.com> wrote:
>
>> I notice there is a meta/recipes-devtools  -  I assume this pulls in from
>> build/downloads - so gcc-5.2.0.tar.bz2 for example. Does the tool-chain
>> comprised of these recipes get built by /usr/bin/gcc before being used to
>> compile Yocto ?
>>
>
> The host's gcc (typically /usr/bin/gcc) is used to build gcc-cross, which
> is then used to compile everything that needs to be cross-compiled.  We
> don't build our own native compiler to replace the host compiler.
>
> Ross
>

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

Re: Which Toolchain is being used to build Yocto ?

[Burton, Ross]

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

On 3 February 2016 at 18:15, Mark T <mtl1nuxd3v@gmail.com> wrote:

> Thanks. That makes sense; all the cross compile tools are built using the
> Host machines native toolchain on the host then the cross-toolchain used to
> cross compile yocto for the target.
>

Correct.

Ross

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

Re: Which Toolchain is being used to build Yocto ?

[Khem Raj]

[-- Attachment #1.1: Type: text/plain, Size: 1204 bytes --]


> On Feb 3, 2016, at 10:15 AM, Mark T <mtl1nuxd3v@gmail.com> wrote:
> 
> Thanks. That makes sense; all the cross compile tools are built using the Host machines native toolchain on the host then the cross-toolchain used to cross compile yocto for the target.
> 
> 
> 
> On 3 February 2016 at 17:13, Burton, Ross <ross.burton@intel.com <mailto:ross.burton@intel.com>> wrote:
> 
> On 3 February 2016 at 15:07, Mark T <mtl1nuxd3v@gmail.com <mailto:mtl1nuxd3v@gmail.com>> wrote:
> I notice there is a meta/recipes-devtools  -  I assume this pulls in from build/downloads - so gcc-5.2.0.tar.bz2 for example. Does the tool-chain comprised of these recipes get built by /usr/bin/gcc before being used to compile Yocto ?
> 
> The host's gcc (typically /usr/bin/gcc) is used to build gcc-cross, which is then used to compile everything that needs to be cross-compiled.  We don't build our own native compiler to replace the host compiler.
> 

you can always use build-appliance if you want to insulate from host dependencies.

> Ross
> 
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


[-- Attachment #1.2: Type: text/html, Size: 2954 bytes --]

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