On Wed, Oct 23, 2013 at 2:01 AM, Rohit2 Jindal
<rohit2.jin...@aricent.com> wrote:
> Hi ,
>
> Actually I am trying to compile our own toolchain by applying our board 
> specific patches to it in yocto . But getting error (attached error log) 
> while running gcc-cross-initial for 4.6.3 toolchain .
>
> I have removed some patches to make it compatible for my own required 
> toolchain patch versions.
>

what are you trying to achieve ? and what version of yocto are you
using. There has been changes in build sequence and it depends on
which version of compiler. So you cant retrofit any version of
compiler with any version of Yocto project with out
major rework

>
> I have changed SRC_URI to download toolchain 4.6.3 tar and removed some 
> patches applicable for 4.7.2 version of toolchain and added my own board 
> specific
> Toolchain patch. Its applying properly but at the compilation time 
> gcc-cross-initial fails I am not able to understand the reason.
>
> I have downloaded binutils 2.22 version for specific to our toolchain patch 
> of binutils_222.patch and removed some patches compatible to 2.23.1 version 
> of binutils .
> Bitbake binutils-cross works fine removing some patches
>
>
> But when I compile bitbake gcc-cross-initial do_compile failed .
>
>
> 1 I am not getting if I want to compile and install my own board specific 
> toolchain I have to run only
>
> Bitbake gcc-cross-initial
> Bitbake gcc-runtime
> Bitbake gcc-cross
>
> 2Please tell whether the above three bitbake commands all are mandatory to 
> compile and install my specific toolchain or which command can be skipped.
>
> 3Please tell its dependency on newlib eglibc uclibc etc I am confused on all 
> these things
>
> 4And please tell the mandatory changes to made for elf toolchain and linux 
> toolchain respectively.
>
> Thanks in advance!!
>
>
> Regards,
> Rohit Jindal
>
>
>
>
>
> ===============================================================================
> Please refer to http://www.aricent.com/legal/email_disclaimer.html
> for important disclosures regarding this electronic communication.
> ===============================================================================
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to